Make the next action explicit
| Task ID | Observed state | Owner | Next action | Resume evidence |
|---|---|---|---|---|
| DOC-27 | Currency absent; nothing written | Finance reviewer | Check original document | Verified currency and unchanged identity |
| DOC-28 | Write timed out; outcome unknown | Integration owner | Search target by task identity | Target record or confirmed absence |
| DOC-29 | Target unavailable | Operations | Pause this dependency path | Dependency restored and retry decision recorded |
Keep the original task identity, failure time and last completed step. A reviewer should not need to reconstruct the whole run. Store a document reference rather than copying invoice contents or credentials into a shared queue.
Close the decision, then resume
- Classify the failure
- Assign the decision
- Verify correction or target state
- Resume the same task
Repeated dependency failures remain paused; do not send every record through a new retry loop.
A timed-out task is found in the destination. Should the reviewer resubmit it?
Show the worked answer
Check that the existing record matches the intended values, mark the write as resolved and continue only the unfinished downstream steps. A mismatch needs a correction decision.