Delivery operations

Once a revision has a decision, the team needs to understand what happened when it was delivered. The learning content item can retain a delivery reference and completed date. An execution attempt records its operation key, attempt number, status, provider reference and failure reason. An operation run carries the source revision and result reference, while ordered steps retain the action and receipt details. Together, these records let the operator investigate a failure without changing the reviewed content to explain it away.

The team traces from the learning item to an attempt or operation run, then into its steps. A queued or running attempt is different from a succeeded or failed one. An unknown outcome needs reconciliation with the external system before repeating the action. The operation key and source revision help distinguish a retry from a new publication decision.

• Read the result. Inspect the attempt status and provider reference before asking for another run.
• Follow the steps. Use each step’s output reference or external receipt to locate the external result.
• Escalate uncertainty. A reconciliation requirement calls for investigation against the source system.

Choose the delivery system and the reference it will return. Define who can request a retry, what counts as a completed publication, and where an external receipt is kept. Establish the procedure for an unknown outcome: the operator checks the provider reference and receipt before another attempt is recorded. Prepare a successful case, a failed case and a case where the external system responded after the team lost its immediate result.

A reviewer approves a lesson revision. An operator checks its delivery result and finds an attempt marked failed. The attempt includes a failure reason and operation key. A related run shows the source revision, and the step trace identifies the action that failed. The operator can investigate the delivery system using the provider reference rather than resubmitting the lesson blindly.

In a second case, the provider shows that a publication succeeded but the immediate response was uncertain. The operator compares the external receipt and operation key with the run before requesting any retry. The result reference is recorded with the run, while the content record carries the delivery reference used by the team. The decision and source revision remain intact.

Rehearse these cases with an operator and the administrator responsible for the delivery connection. Ask them to start from a content number, locate the attempt, identify the run revision and find the receipt. The analyst should be able to read the final status without mistaking an unknown attempt for a confirmed delivery.

• Failed attempts — Publication attempts with a failure reason for investigation.
• Runs requiring reconciliation — Runs whose external result must be checked.
• Delivered content — Items with completed dates and delivery references.

Follow correction and delivery and review integrations before the first release.