Execution history

Operation Runs identify an action by operation key, source revision, start and completion time, status and input hash. Numbered Operation Steps record the action name, input and output references, external receipt and status. Execution Attempts preserve attempts against a form revision and operation key, including provider reference and failure reason. State History records the transition, actor, source revision and reason.

The run and its numbered steps explain which source revision an action used and whether it succeeded. Attempts record repeated execution against an operation key. A failed or uncertain attempt calls for an inspection of its reference and reason before anyone tries the action again.

• Identify the operation. Start with the source form, revision and operation key.
• Inspect each step. Follow numbered inputs, outputs, status and any external receipt.
• Resolve uncertainty. Compare attempts and state history before recording another action.

The Operator agrees how to identify a repeated request and who investigates a failed or uncertain result. A run marked reconciliation required calls for checking the recorded steps and any external receipt before taking another action. A failed attempt and its reason are evidence for diagnosis; they should not be mistaken for a completed publication or accepted submission.

Agree how the Operator distinguishes a retry from a new action. A run marked reconciliation required needs a check of its steps and receipts. Keep the source revision on the run so the team can trace which definition was published, accepted or superseded.

Publish a validated form in a rehearsal and inspect the resulting run, its numbered steps and the state transition. Next, inspect a failed attempt and confirm that the source revision and operation key identify the affected action. For a documented correction, keep the prior run visible and compare it with the successor Draft revision.

Compare the publish run with its state transition and the later correction run. The correction leaves the earlier run in place and starts a successor Draft. For a failed attempt, inspect its reason and provider reference before retrying.

• Failed operation runs — Inspect Failed and reconciliation required runs by source revision and reason.
• Execution attempt queue — Follow Queued, Running and Unknown attempts by operation key.

See definition and publication and submission review for the decisions that connect this module to the next one.