These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Learning Management System
- Features
- Delivery and provenance
Delivery and provenance
Trace recorded delivery attempts, steps, and reconciliation work.
OverviewRuns Needing Reconciliation×
Learning Management System · Delivery and provenance
New
Runs Needing Reconciliation
Operation runs
| Source | Operation key | Source revision | Started at | Result reference | Status | |
|---|---|---|---|---|---|---|
| ENR-23254 | OK-383 | 740 | 14 Oct | RR-965 | Reconciliation required | |
| ENR-20070 | OK-771 | 180 | 21 Oct | RR-832 | Reconciliation required | |
| ENR-29932 | OK-550 | 460 | 14 Oct | RR-373 | Reconciliation required | |
| ENR-30675 | OK-690 | 500 | 19 Oct | RR-239 | Reconciliation required | |
| ENR-68789 | OK-294 | 260 | 06 Oct | RR-550 | Reconciliation required |
6 of 6 records
OK-383Operation runs · OR-96126
Reconciliation requiredSourceENR-23254
Source revision740
Started at14 Oct
Result referenceRR-965
What you can do
Connect a decision to its execution record
A delivered enrollment carries a completion date and delivery reference. Operation runs store an operation key, source revision, input hash, status, result reference, and failure reason. Ordered steps retain action names, input and output references, receipt details, and evidence. Execution attempts record retry numbers, provider references, status, and failure reasons. Together these records help staff explain what happened after approval.
How the work is organized
A reviewer should check the approved decision and source revision before a delivery is treated as complete. A run may be Queued, Running, Succeeded, Failed, or reconciliation required. A failed or uncertain attempt needs investigation against the operation key and provider reference. Repeating the action without examining the earlier result can create a duplicate external effect.
- Match the revision. Tie the operation run back to the enrollment version the reviewer approved.
- Read the steps. Use step order, output reference, and receipt evidence to find the point of failure.
- Reconcile uncertainty. Investigate a failed or unknown result before another attempt is made.
What to agree during setup
Define what constitutes delivery for each course and which external source provides an acknowledgement, if any. Agree how operation keys are formed and who investigates a run requiring reconciliation. Decide whether the completion date comes from an external acknowledgement or an authorized internal decision. Test a successful result, a failed attempt, and a repeated request with the same operation key.
Check the handoff on an actual case
A reviewer approves a learner’s completed enrollment. The delivery operation records a run and a sequence of steps, but the last external receipt is uncertain. The operator opens the run and compares its result reference with the attempt’s provider reference. The team confirms the external outcome before another delivery is attempted. A visible Delivered label alone would not explain whether the receiving system accepted the action.
For a second learner, the operation succeeds and the enrollment receives its delivery reference. Later, someone asks which revision was approved and which receipt belongs to it. The run’s source revision and step evidence should lead back to the reviewer decision. Rehearse that trace from enrollment to decision to run and receipt with staff who will answer those questions.
What your team sees
- Runs Needing Reconciliation — Operations whose outcome needs investigation against a source enrollment.
- Failed Execution Attempts — Failed attempts with operation key, attempt number, and failure reason.
Follow the work through
What it keeps track of
Data model- Operation runs
- Workflow-maintained execution runs with operation key, input hash and persisted result reference.
- Operation steps
- Ordered steps inside an operation run with input, output and external receipt state.
- Execution attempts
- Each recorded attempt to execute an approved action for a service application.
- Enrollments
- Learner enrollments submitted for completion, review and certification.
- Review decisions
- Independent reviewer decisions recorded against an exact source revision.
Who uses it
Permissions- Learning Management Operator
- , Learning Management Reviewer, Read Only Analyst.
- The operator investigates an execution exception, the reviewer confirms decision authority, and the analyst reads authorized outcomes.
Set up Learning Management System your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.