{"version":"2.1.319","anchor":"workflow-structured-output-verdict-gets-a-no-copy-outcome","canonical_anchor":"workflow-structured-output-verdict-gets-a-no-copy-outcome","heading":"Workflow output checks report a new outcome when no written copy exists","tier":"internal","area":"Workflows","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/workflow-structured-output-verdict-gets-a-no-copy-outcome","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### Workflow output checks report a new outcome when no written copy exists\n\nThe check on a workflow step's structured output now reports `no_copy` when no written copy exists, and decides the last step differently\n\n**Unclear.** Whether workflows now behave differently, beyond how the check is reported, is not clear.\n\n**What**\n\nIn a workflow, a step can be expected to return structured output, meaning answers in a fixed format. Claude Code checks whether that output was produced. Two things about that check changed:\n\n- It now reports the outcome `no_copy` when no written copy of the output exists.\n\n- It decides whether a step is the last one by looking at response ids and rows, where before it compared a response number.\n\n**Why**\n\nThe information Claude Code records about these checks has a different shape, and the way it picks the last step may change how some workflows finish.\n\n- Area: Workflows\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}