{"version":"2.1.247","anchor":"workflow-agents-that-finish-with-no-result-now-fail-loudly","canonical_anchor":"workflow-agents-that-finish-with-no-result-now-fail-loudly","heading":"Workflow agents that finish with no result now fail loudly","tier":"notice","area":"Workflows","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247\/e\/workflow-agents-that-finish-with-no-result-now-fail-loudly","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.247","markdown":"### Workflow agents that finish with no result now fail loudly\n\nA workflow agent that finished with nothing now raises a clear error instead of passing an empty result on.\n\n**What**\n\nIn workflow v2 runs, an agent that was skipped, blocked, or gave up after retries used to pass its empty result along as a value. It now raises a descriptive error instead.\n\n**Details**\n\n- Cleanup also sweeps retracted setup-script facts along with failed and finished ones.\n\n**Evidence**\n\n`agent produced no result (skipped, blocked, or gave up after retries)`\n\n- Area: Workflows\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5"}