Durable execution

The execution workflow starts from a reviewed revision and persists an execution, an operation run, a confirmed step receipt and an execution attempt. It marks the run Succeeded after confirmed output and updates the definition’s execution result. The Operations Operator can follow that path from the source record to the outcome without treating a visible status as the whole proof.

The source record identifier is required on an execution. The definition version and operation key let the team compare the intended input with the operation that was carried out. Keep the parent definition linked to the run. A later definition revision should not make an earlier execution look as though it used the new instructions.

• Execution. The source identifier and parent definition establish what request was processed.
• Operation run. The key, revision, status and result reference record the durable operation.
• Confirmed output. The step receipt and result carry the evidence needed to assess success.

Define where source identifiers come from and how the team handles repeated requests. Decide whether the provider reference or result reference is the external reconciliation key. Set a retry policy on the definition that the Operations Operator understands before starting a run. Agree which failed or uncertain outcomes require investigation rather than another immediate attempt.

Choose a pilot source record that can be checked in the connected service. Keep its input schema and definition version. After execution, compare the local result with the outside receipt and record the business outcome on the execution. If the result differs, use the run and step trace to locate the gap before another action is taken.

A reviewed definition processes a request that has a stable source record identifier. The Operations Operator starts its run and later checks the accepted outcome against the operation result reference. The corresponding step has an external receipt, and the attempt shows when the provider call finished. The definition’s latest result gives the owner a quick summary, while the linked records explain how it was reached.

Now rehearse a repeated request with the same source identifier and operation key. The team should inspect the prior run and receipt before deciding whether another attempt is safe. If the provider outcome is uncertain, record the exception for reconciliation. Do not infer a successful external action solely from a local status.

• Execution outcomes — Match each source record to its parent definition and recorded outcome.
• Run status board — Find queued, running, successful and exceptional operations.
• Runs requiring attention — Investigate failures and reconciliation work with the original key.

Read durable execution and receipt and exception review for the run and its evidence.