{"version":"2.1.317","anchor":"workflow-progress-finalized-on-end","canonical_anchor":"workflow-progress-finalized-on-end","heading":"Workflow progress is finalized when a local workflow ends","tier":"notice","area":"Elsewhere","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/workflow-progress-finalized-on-end","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Workflow progress is finalized when a local workflow ends\n\nWorkflows now track which agents started and, when a local workflow ends, mark leftover steps with the final status before saving output\n\n**What**\n\nA workflow runs a series of steps, some of them carried out by agents (helper instances of Claude). Two changes affect how its progress is recorded:\n\n- `startedAgentIndexes`: workflow progress now stores the set of agents that have started.\n\n- Finalizing on end: when a local workflow ends, any progress still being held back is written out first. Remaining steps are then marked with the workflow's final status, such as `completed`, using `startedAgentIndexes`. The workflow output file is written from this finalized progress. Before, the progress was written exactly as it stood.\n\n**Why**\n\nIn practice, a finished workflow's saved progress now reflects how it ended, rather than leaving some steps looking as if they were still running.\n\n- Area: Elsewhere\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}