A run is pinned to the workflow version it started with #2014
Notifications
Due Date
No due date set.
Blocks
Reference: sam/archie#2014
Reference in new issue
Block a user
A run that waits for days resumes on whatever workflow code is deployed when it wakes. A step added, removed or reordered in between makes the replay take a different path, or fail as non-deterministic with no hint that a version change was the cause. The run never records which version of the workflow it began under.
Wanted: a workflow declares a version next to its registration, a run records the version it started with, and a run whose workflow version has changed is not executed against the new code. It is held or failed with a reason naming both versions, or resumes on the old version if that code is kept.
Done when: a run records its workflow version, a resumed run whose workflow version differs is stopped with a clear reason (or resumes on the old version), the trail and run view show the version, and a test over the claim path proves the check. Evidence: durable-execution evaluation, requirement 6 (#1997).
Done (
400699cfb): workflows register with a version, each run records the version it started with, and a run whose workflow version changed fails clearly naming both versions instead of resuming down a different path. The run view shows the version.