Resuming after human review should continue the approved current operation, not replay everything that happened before the pause. Preserve completed steps and recheck facts that may have changed while the reviewer was deciding.
Resume is a controlled transition
A review-resume workflow accepts an authorised decision and determines the next eligible action. It should distinguish approved, denied, expired, cancelled, and clarification-required outcomes.
For a proposed record, bind the decision to the proposal revision, operation identity, reviewer, and relevant resource versions. The executor resolves that record through trusted state and performs current permission and prerequisite checks.
Do not treat an approval callback as an instruction to start the workflow from the beginning. Earlier notifications or writes may already have completed. Resuming should use the durable step ledger and preserve duplicate-protection identities.
Follow a fictional appointment hold
An AI proposes a booking that needs staff review. While the request waits, the temporary slot hold expires. The reviewer approves the old proposal. The workflow should check current availability and explain that the original time is no longer established, rather than create an overbooked appointment.
A second fixture leaves the hold valid but delivers approval twice. The operation should resume once and return the existing result for the repeated decision. The customer should not receive duplicate confirmations.
| Resume condition | Required behaviour |
|---|---|
| Approved current proposal | Continue through final checks |
| Resource changed during review | Conflict or fresh review path |
| Decision denied | No proposed effect |
| Approval callback repeated | Same logical continuation |
| Worker restarts after external effect | Reconcile before repeat execution |
Use controlled waiting intervals and authoritative record assertions. A workflow turning green after resume does not prove that it preserved the intended time, customer, or effect count.
Explain pending work accurately
The staff and caller views should distinguish approved from completed. Approval can still be followed by a validation failure, unavailable slot, or external outage. Return an explicit outcome and next owner instead of silently abandoning the request.
Revalidation can make an approval appear ineffective when facts change quickly. That friction is real but necessary for correctness. Improve proposal timing or reservation policy rather than bypassing freshness checks to honour stale decisions.
This resume design is proposed. The voice integration case study provides related workflow context. Pair it with durable workflow state.
Review-resume FAQ
Does approval guarantee execution succeeds?
No. Current prerequisites and external systems still determine the effect.
Should the workflow replay previous steps?
Only steps that remain eligible under the durable state and duplicate-protection policy.
What should happen when the proposal is stale?
Preserve the decision history, explain the changed condition, and obtain a fresh proposal or authorised resolution.