Workflow guide
A long-running job needs a human decision before its next consequential step.
Prepare the result, pause at a review checkpoint, and resume only after an explicit decision about the same revision.
Evidence: pinned-primary-documentation-screen. Recorded: 2026-10-13.
A draft or job output is ready, but publication or another consequential next step still needs an authorized human decision.
- Prepare the draft and identify its exact version. Keep the consequential action paused.
- Show the result and the proposed next action to the decision owner. Record a deadline.
- Collect approve, reject or request-changes against that version. In a running system, a wait token can carry the response; a manual queue can record the same decision.
- Before resuming, check that the owner, version and deadline still match. Changed work needs a fresh decision.
- Resume the approved step once, or leave rejected and expired work paused. Record the outcome and a correction path.
Check your result
In a synthetic rehearsal, only a current approval for the reviewed version permits the next step. Rejection, expiry, wrong owner, changed version and repeated responses produce no extra action. This rehearsal is proposed, not completed.
Limits
- The source describes a runtime mechanism, not proof of reviewer identity or decision quality.
- The Trigger.dev implementation requires its SDK and service; the manual variant below does not reproduce that runtime.
- Revision binding, reviewer authority and effect deduplication below are local safeguards proposed by this guide, not guarantees established by the upstream token API.
- No upstream runtime, installation, local reproduction or consumer adoption was performed.
Pinned upstream review example · Stage gates guide · Workflow evidence contract