Reconcile a shift exception

Compare operation receipts with actual effects before resolving a failed or pending result.

Step by step

Open exception Operations Manager

Operations Manager uses Shift Operations to open the underlying failed or review-needed operation receipt and parent order.
- Failed attempt located
- Updates Operation receipts, Stop orders
Read the attempt Operations Manager

Compare the action, operation key, expected revision and occurrence time with the order's current records.
- Revision and decision context checked
- Updates Operation receipts, Line tickets, Review decisions
Check effects Operations Manager

Compare linked local effects and any external reference with the expected identity, scope and quantities. Read before considering another execution.
- Actual local and external effects compared
- Updates Stop order lines, Payment evidence, Stop fulfillment events
Attach evidence Operations Manager

Record the actual supporting file or reference on the parent order with the appropriate visibility.
- Supporting evidence retained
- Updates Record attachments, Stop orders
Resolve result Operations Manager

Mark the receipt completed only when its expected effects match. Leave a missing or conflicting effect visible for review.
- Matching result completed or exception retained
- Updates Operation receipts

And how to keep it from happening.

A timeout is interpreted as proof that an external action did not happen.
A receipt is closed because an order status changed, without matching quantities.
A retry uses a new key and duplicates a payment or release effect.
Evidence is attached to a different parent order.

Start free, then use Proto to change fields, steps and approvals before your team goes live.