Execution trace

An execution attempt records the operation key, attempt number, status, provider reference and failure reason for a packet. A run records the packet revision, input hash, start and completion times, result reference and final state. Steps within the run identify the action, input and output references, external receipt and receipt date. These records help operations separate a provider failure from an unknown result that requires reconciliation.

• Attempt. Find the packet and operation key before trying an action again.
• Run. Keep the source revision and input hash with the overall outcome.
• Step. Inspect the receipt and action that produced a result or exception.

Agree how a provider operation key is assigned and reused for retries. Define which provider acknowledgement counts as accepted evidence, and what to do when a response is unknown. Keep a failed attempt visible with its reason. Review a run marked reconciliation required before resending work, because a provider may have completed an action even when the first response was lost.

A packet preparation call starts but its provider response times out. The execution attempt shows Unknown while the run has a source revision and input hash. Operations checks the operation key and provider reference before issuing another attempt. The step receipt can establish whether an envelope was actually created. If it was, the team reconciles the original run and records the result reference. If it failed, a new attempt can proceed with the same packet context and an understandable reason.

The handoff should be checked on a real packet, not just on a status label. Open the linked record and compare the people, revision and provider evidence behind the decision. If the record is returned or uncertain, keep it visible to the person responsible for the next action. The next team should be able to explain what was received, what was accepted and why the packet changed state.

Start an investigation with the attempt’s operation key and packet link. The run identifies the source revision and input hash; its steps identify the external receipt, if one was returned. A failed attempt and an unknown attempt require different decisions: the unknown result may already have created a provider envelope. Compare the original reference with the provider before another attempt is made. Record the reason for any follow-up so the next operator can see which response was checked and why the packet is still waiting.

• Execution Attempts Queue — Queued, running, failed and unknown attempts requiring attention.
• Operation Run Exceptions — Runs whose result needs investigation or reconciliation.

Follow packet preparation and signer verification.