{"version":"2.1.265","anchor":"workflow-resume-now-validates-the-target-run-before-compilin","canonical_anchor":"workflow-resume-now-validates-the-target-run-before-compilin","heading":"Workflow resume now validates the target run before compiling the script","tier":"notice","area":"Workflows","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/workflow-resume-now-validates-the-target-run-before-compilin","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Workflow resume now validates the target run before compiling the script\n\nResuming a workflow now checks the target run is actually finished before compiling its script\n\n**What**\n\nWhen resuming a workflow by its run ID, Claude Code now checks upfront whether that run is still active - either \"running\" or \"paused\" without having actually exited - and refuses to resume if so, with the message that resuming now would run two copies of its agents against the same journal. It also now waits for the run's journal to finish being written before proceeding. Previously, this check only happened after the workflow script had already been compiled.\n\n**Why**\n\nChecking earlier avoids wasted work compiling a script for a resume that's going to be rejected anyway, and prevents accidentally running two sets of agents against the same underlying run at once.\n\n- Area: Workflows\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}