{"version":"2.1.265","anchor":"workflow-tool-gains-resumefromrunid-reads-a-stored-run-jour","canonical_anchor":"workflow-tool-gains-resumefromrunid-reads-a-stored-run-jour","heading":"Workflow tool can resume a run from resumeFromRunId alone","tier":"use","area":"Workflows","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265\/e\/workflow-tool-gains-resumefromrunid-reads-a-stored-run-jour","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.265","markdown":"### Workflow tool can resume a run from resumeFromRunId alone\n\nThe Workflow tool can now recover and restart a script using just a stored run id, without needing the script path\n\n**What**\n\n- `Workflow`'s `validateInput`\/`checkPermissions` now handle a `resumeFromRunId` input: when the script path can't be resolved, they look up the stored run's journal via the run id, and reconstruct the script to run from it.\n\n- If the resume lookup fails, the tool can now return a \"refused\" outcome instead of erroring out unclearly.\n\n- The background-workflow notification text was updated to say to relaunch with `Workflow({scriptPath, resumeFromRunId})` using the run id from the summary, instead of showing a literal resumeFromRunId value.\n\n**Why** This lets you resume an in-progress or interrupted workflow run using just the run id reported earlier, without needing to track down or retype the original script path.\n\n- Area: Workflows\n- Names: `resumeFromRunId`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 2\/5"}