{"version":"2.1.323","anchor":"workflow-completion-carries-a-refusedagentnote","canonical_anchor":"workflow-completion-carries-a-refusedagentnote","heading":"Turn results and workflow completions now carry a note about refused agents","tier":"notice","area":"Workflows","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323\/e\/workflow-completion-carries-a-refusedagentnote","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.323","markdown":"### Turn results and workflow completions now carry a note about refused agents\n\nWhen an agent is refused, a `refusedAgentNote` is now attached to turn results and workflow completion messages; failed MCP calls are counted\n\n**What**\n\nAgents are helpers Claude can start to work on part of a task, and workflows run several of them. Claude Code now records when one of them was refused:\n\n- A turn result, the record made when Claude finishes responding, now carries `refusedAgentNote`.\n\n- A workflow's completion message now includes `refusedAgentNote`, unless script content is held back from SDK events (the messages sent to programs that embed Claude Code).\n\n- A new `failedMcpCallCount` field counts failed calls to MCP servers (outside services that give Claude extra tools) and is added to the stats record when above 0.\n\nWorkflows also start a second repeating timer, cleared when they finish.\n\n**Why**\n\nIn practice, information about a refused agent now travels with the results, so Claude can be told that part of the work did not run.\n\n- Area: Workflows\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}