Operation trace

A document’s current status tells the team where it stands. The operation records explain how a revision reached that state. A run links the source document and source revision to an operation key, start and completion dates, result reference and status. Numbered steps retain the action name, their own status and any external receipt. Attempt records preserve retries and provider references separately.

Suppose publication appears complete locally but the connected destination times out. The Publishing Manager can inspect the run and step trace for an external receipt, then compare the attempt’s provider reference and failure reason. An unknown result needs reconciliation against the original action. Creating another publication attempt without that check risks a duplicate external effect and an unclear audit trail.

• Run. The operation key and source revision identify the document change under examination.
• Step. Each numbered action records input and output references and any receipt evidence.
• Attempt. The attempt record shows whether execution was queued, running, successful, failed or unknown.

Choose stable operation keys and identify the external systems that may issue receipts. Agree which person investigates a failed or reconciliation-required run, where the external source can be checked and which evidence must be attached. The mapping record for source fields should be reviewed before data is moved into controlled documents, particularly where transformations alter identity or classification.

Define what can be retried and when a correction is required instead. A correction creates a successor version and a compensating step while retaining the original record. The run history must remain understandable to a reviewer who did not execute the action. State history should identify the prior and new document status, actor, revision and reason.

Select a reviewed document that has an approval operation. Compare the source revision in the run with the document revision and the review decision. Inspect each step in order, checking any receipt ID and attached evidence. If the run failed, use its failure reason and the attempt record to determine what happened before acting again.

Rehearse an uncertain external result. The manager checks the connected destination using the recorded reference, then updates the operational outcome through the agreed process. The team should be able to tell whether the content was accepted, needs another attempt or needs a documented correction. The status and history must tell the same story.

• Runs needing reconciliation — Investigate operations whose external outcome needs confirmation.
• Execution attempts — See queued, running and failed attempts by start and finish time.
• Document register — Return to the current source document and revision.

Follow the execution review process and the correction process.