Orchestrate subagents at scale with dynamic workflows changedworkflows
Nearest release: v2.1.322, published 4 hours before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.
Upstream edited this page at 10 Nov 2026 06:21 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 10 Nov 2026 06:37 UTC.
Upstream edited
Recorded here
Lines+11added
Lines−5removed
From line
371
where the diff opens
First seen
14 Aug 2026
this site's first read of the page
Recorded edits52to this page, all time
The whole hunk
from line 371, old and new numbered
/
from line 371
371371
372372 Before v2.1.305, completed agents could also run again when you relaunched an unedited script whose `pipeline()` items or `parallel()` tasks ran more than one agent each. To stop those reruns for new runs, update Claude Code.
373373* **Still running when you stopped**: starts over. Stopping the whole run doesn't count any agent as failed.
374* **[Failed at a usage limit](#when-a-run-hits-your-usage-limit) on v2.1.318 or later**: runs again, and agents that completed return their saved results. If your script called another agent after the failure and that agent returned a result, every agent the script starts after the failed one also runs again.
374375* **Failed**: runs again, and so does every agent the script starts after it, even ones that completed. Stopping one agent alone, by selecting it in [`/workflows`](#watch-the-run) and pressing `x`, counts as failing.
375376
376That last case means a failure in the middle of a fan-out reruns work that already finished. If a script starts A, B, C, and D in that order and B fails, relaunching returns A from cache and runs B, C, and D again.
377That last case means a **Failed** agent in the middle of a fan-out reruns work that already finished. If a script starts A, B, C, and D in that order and B is **Failed**, relaunching returns A from cache and runs B, C, and D again.
377378
378379If you edit a script that started A, B, C, and D so that it starts A, C, B, and D, the second agent to start is now C, where the previous run started B. Relaunching returns A from cache and runs C, B, and D again.
379380
from line 392
391392
392393### When a run hits your usage limit
393394
394When an agent hits your claude.ai [usage limit](https://code.claude.com/docs/en/interactive-mode.md#wait-for-a-usage-limit-to-reset), the run pauses rather than failing that agent: the agents that hit the limit wait for the reset, and no new agents start. Shortly after the limit resets, the waiting agents run again and the run continues on its own. Requires Claude Code v2.1.271 or later; on earlier versions, the affected agents fail.
395When an agent hits your claude.ai [usage limit](https://code.claude.com/docs/en/interactive-mode.md#wait-for-a-usage-limit-to-reset), the run pauses rather than failing that agent. The agents that hit the limit wait for the reset, and no new agents start. Shortly after the limit resets, the waiting agents run again and the run continues on its own. Requires Claude Code v2.1.271 or later, or [v2.1.319 or later](https://code.claude.com/docs/en/desktop.md#claude-code-version-in-the-code-tab) in the Desktop [Code tab](https://code.claude.com/docs/en/desktop.md). On earlier versions, the affected agents fail.
395396
396While the run waits, its progress line in the task panel and the [`/workflows`](#watch-the-run) header show when the limit resets.
397While the run waits, its progress line in the task panel and the [`/workflows`](#watch-the-run) header show when the limit resets. In the Code tab, the run shows a line such as `Paused at usage limit · continues after 3:45 PM if the app stays open`. Keep the app open.
397398
398399The run pauses only when all of these hold; when one doesn't, the affected agent fails instead:
399400
400* The session is interactive and signed in with a claude.ai subscription. A run doesn't pause in [non-interactive mode](https://code.claude.com/docs/en/headless.md) with `claude -p` or the [Agent SDK](https://code.claude.com/docs/en/agent-sdk/overview.md), in a [background session](https://code.claude.com/docs/en/agent-view.md), or in a [Remote Control](https://code.claude.com/docs/en/remote-control.md) or [agent team](https://code.claude.com/docs/en/agent-teams.md) teammate session.
401* The session is signed in with a claude.ai subscription without [usage-based billing](https://code.claude.com/docs/en/interactive-mode.md#start-a-wait-yourself), and is one of these session types:
402 * An interactive terminal session. A run doesn't pause in [non-interactive mode](https://code.claude.com/docs/en/headless.md) with `claude -p` or the [Agent SDK](https://code.claude.com/docs/en/agent-sdk/overview.md), in a [background session](https://code.claude.com/docs/en/agent-view.md), or in a [Remote Control](https://code.claude.com/docs/en/remote-control.md) or [agent team](https://code.claude.com/docs/en/agent-teams.md) teammate session.
403 * A local session you started in the Code tab. A run doesn't pause in an SSH, WSL, [Dispatch](https://code.claude.com/docs/en/desktop.md#sessions-from-dispatch), or [scheduled task](https://code.claude.com/docs/en/desktop-scheduled-tasks.md) session, in one started from Remote Control or through a [corporate launcher](https://code.claude.com/docs/en/corporate-launcher.md), or while [`CLAUDE_CODE_DISABLE_NONESSENTIAL_TRAFFIC`](https://code.claude.com/docs/en/env-vars#variables) is set.
401404* [`autoContinueAtUsageLimit`](https://code.claude.com/docs/en/settings-reference#autocontinueatusagelimit) is on, the same setting that lets the session itself [wait for a usage limit to reset](https://code.claude.com/docs/en/interactive-mode.md#wait-for-a-usage-limit-to-reset). If you turn it off during a wait, the wait ends and the waiting agents fail.
405* In the Code tab, the **Auto-continue when limits reset** checkbox on a [session-limit card](https://code.claude.com/docs/en/errors.md#youve-hit-your-session-limit) is checked, as it is by default. If you uncheck it, runs in your Code tab sessions stop pausing, unless managed settings set `autoContinueAtUsageLimit` to `true`.
402406* The limit resets within 24 hours. A weekly limit can reset further out.
403407* The run hasn't already waited twice. When it hits the limit a third time, the agent fails.
408
409To finish a run whose agents failed at the limit, ask Claude to [relaunch the workflow](#which-agents-run-again) after the limit resets.
404410
405411### When an agent stalls and restarts
406412
No line in this hunk matches that.