{"version":"2.1.292","anchor":"workflow-resume-guards-for-hidden-scripts","canonical_anchor":"workflow-resume-guards-for-hidden-scripts","heading":"Resuming a workflow run stops if its hidden script is missing or was edited","tier":"notice","area":"Workflows","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/workflow-resume-guards-for-hidden-scripts","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Resuming a workflow run stops if its hidden script is missing or was edited\n\nA workflow run that hides its script can now be resumed only with its original, unedited script file; otherwise you are told to start a new run\n\n**What**\n\nWhen you resume a workflow run, Claude Code now checks its script first. If the run hides its script and that script is not loaded, or the script file has been edited, the resume stops with a clear error. The error says the run can only be resumed with its original, unedited script file, and tells you to start a new run without `resumeFromRunId`.\n\n**Why**\n\nThis stops a run from continuing with a script that is different from the one it started with. If you change a hidden workflow script, start a fresh run instead of resuming.\n\n- Area: Workflows\n- Names: `resumeFromRunId`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}