Goal
Build a backend flow that survives retries and external waiting.Prerequisites
- A handler route exposed to StackShift
Workflow
Onboarding workflow
This flow creates a user, sends email, waits for verification, then unlocks the account.Resume behavior
- Before the wait, completed step results are saved.
- While waiting, the run is not consuming compute.
- When the matching event arrives, StackShift invokes the handler again with the event result.
- Completed steps return their saved outputs and the job continues after the wait.
Failure handling
- If a step throws, the run is retried according to its retry policy.
- Completed steps are not repeated on retry.
- If the wait times out, StackShift follows the configured timeout behavior.
Expected result
A multi-step job resumes from saved state instead of starting over.
Related guides
Event Waiting + Correlation
Pause a workflow until the right external event arrives, then resume the correct run.
Retries & Failure Handling
Durable Jobs retries transient failures, preserves completed steps, and gives failed work a clear recovery path.