{"version":"2.1.285","anchor":"workflow-swallows-unhandled-promise-rejections","canonical_anchor":"workflow-swallows-unhandled-promise-rejections","heading":"Workflow scripts no longer crash on an unhandled failed agent call","tier":"notice","area":"Workflows","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/workflow-swallows-unhandled-promise-rejections","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Workflow scripts no longer crash on an unhandled failed agent call\n\nWhen a workflow script leaves a failed agent(), parallel(), pipeline() or workflow() call unhandled, Claude Code logs it and keeps running\n\n**Unclear.** Whether the handler also catches unhandled failures from outside workflow scripts is not settled.\n\n**What**\n\nWorkflow scripts can call `agent()`, `parallel()`, `pipeline()` and `workflow()`. Each call hands back a promise, a placeholder for a result that arrives later. If one of those calls fails and the script never deals with the failure, Claude Code now logs \"Workflow: swallowed an unhandled rejection (not exiting)\" and keeps running instead of exiting.\n\n**Why**\n\nA forgotten failure in a workflow script no longer takes down the whole process. Look for that log line if a step seems to vanish silently.\n\n- Area: Workflows\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 1\/5"}