{"version":"2.1.292","anchor":"workflow-v2-run-refuses-to-withhold-its-script-script-hash","canonical_anchor":"workflow-v2-run-refuses-to-withhold-its-script-script-hash","heading":"Workflows that withhold their script from SDK events resume with the unedited script","tier":"notice","area":"Workflows","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/workflow-v2-run-refuses-to-withhold-its-script-script-hash","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### Workflows that withhold their script from SDK events resume with the unedited script\n\nWorkflow runs with `withholdScriptFromSdkEvents` now record the script's hash, offer resuming only with the unedited script, and are refused for v2 runs\n\n**What**\n\nA workflow is a scripted multi-step run. The `withholdScriptFromSdkEvents` setting keeps a workflow's script out of the events sent to programs built on the SDK. Its handling changed.\n\n- Starting a v2 workflow run with `withholdScriptFromSdkEvents` set now fails with \"A workflow v2 run cannot withhold its script\".\n\n- When the script is withheld, its sha256 hash (a fingerprint of the file) is stored for each run id.\n\n- The v1 runner gets a `withholdScript` option, replacing `indexLabelsForUnlabelledAgents`, which was set from the same value before.\n\n- With the setting on, workflow notifications say \"To resume with the unedited script\" and drop the hint about re-running with edits. Before, they always said \"To resume after editing the script\". Adopted workflows carry the setting.\n\n**Why**\n\nWhen a script is hidden from SDK events, the program watching cannot see or edit it, so resuming is offered only with the original script. Hosts that set this on a v2 run will now get an error.\n\n- Area: Workflows\n- Names: `withholdScriptFromSdkEvents`\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}