A crash mid-action marks the action unknown #2015
Notifications
Due Date
No due date set.
Blocks
Reference: sam/archie#2015
Reference in new issue
Block a user
A connector action records its result as a step after the effect. If the process dies between the effect and the recorded result, the resume finds no step and runs the action again, repeating an effect that may already have happened.
Wanted: record a started step before a connector action's effect. On resume, a started step with no result marks the action unknown instead of re-running it, the same way an action whose outcome a connector cannot confirm is already handled.
Done when: killing the binary during an action leaves that action unknown in the trail, it is not retried, and the owner is told. Evidence: durable-execution evaluation, requirements 2 and 3 (#1997).
Done (
85e6f8eb4): a started marker is recorded before a non-read-only action executes on both the unattended and approved paths; on resume an action with a marker and no result is reported unknown, never run again, and the owner is notified. Covered by a table test; not yet exercised by killing the live binary.