{"version":"2.1.305","anchor":"workflow-result-log-tracks-demoted-and-replaced-results","canonical_anchor":"workflow-result-log-tracks-demoted-and-replaced-results","heading":"Workflow records now track steps that were re-run or superseded","tier":"internal","area":"Workflows","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305\/e\/workflow-result-log-tracks-demoted-and-replaced-results","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.305","markdown":"### Workflow records now track steps that were re-run or superseded\n\nA workflow's record now notes results that a re-run step superseded, and drops a result when the same step later fails\n\n**Unclear.** What resuming or replaying a workflow does differently with these tracked results is not stated.\n\n**What**\n\nClaude Code keeps a running record of each workflow's steps. That record used to note only which steps started, finished with a result, or failed. It now also notes:\n\n- results that were demoted, because the same step started again after it had a result\n\n- results that were replaced, because the same step produced a second result\n\nA result is also removed when a later failure arrives for the same step, rather than being left in place.\n\n**Why**\n\nThis changes how re-run steps are treated when a workflow is read back, for example when it is resumed.\n\n- Area: Workflows\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}