{"version":"2.1.286","anchor":"workflow-agents-treat-a-silent-response-stream-as-a-stall-an","canonical_anchor":"workflow-agents-treat-a-silent-response-stream-as-a-stall-an","heading":"Workflow agents report a lost reply when the response goes silent","tier":"notice","area":"Workflows","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286\/e\/workflow-agents-treat-a-silent-response-stream-as-a-stall-an","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.286","markdown":"### Workflow agents report a lost reply when the response goes silent\n\nWhen a workflow agent's response stream goes silent, Claude Code now reports a lost reply, retries, and gives a specific error if all tries fail\n\n**Unclear.** What makes Claude Code give up on the stream, and the value of the new cap, are not known.\n\n**What**\n\nA workflow agent is a helper agent that Claude Code runs as one step of a workflow. When the stream carrying its reply goes silent and Claude Code gives up waiting, the agent now:\n\n- treats it as a stall and stops that attempt\n\n- reports `reply lost - the response stream went silent and Claude Code gave up waiting for it` instead of the generic message that it stalled with no progress\n\n- marks the result as a lost reply and retries\n\n- if every attempt loses its reply, fails with an error saying the agent lost its reply on all attempts, instead of the generic abandoned error\n\nThe point at which a stalled attempt is retried is also capped, rather than always being half the stall time.\n\n**Why**\n\nIf you run workflows, a failure now tells you the reply was lost to a silent stream, and a stuck step is retried sooner.\n\n- Area: Workflows\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}