Group of 2 You'll notice Notable
No documentation found
The Workflow tool can now recover and restart a script using just a stored run id, without needing the script path
What
Workflow'svalidateInput/checkPermissionsnow handle aresumeFromRunIdinput: 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.- If the resume lookup fails, the tool can now return a "refused" outcome instead of erroring out unclearly.
- 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.
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.
Names in the bundleresumeFromRunId
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up resumeFromRunId, on Agent SDK reference - TypeScript.
| `runId` | `string` | Workflow run identifier to pass as `resumeFromRunId` on a later invocation. Absent for `remote_launched` runs, where the cloud session URL is the resume handle |agent-sdk/typescript see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up resumeFromRunId, on Agent SDK reference - TypeScript.