Run the process past the end of the request.
Declare the steps, waits, retries, failures, and human decisions. The Swirls runtime checkpoints the run and keeps its history.
Long-running work needs state beyond one request.
A process may wait for the clock, another system, or a person. Swirls keeps the declared sequence and preserves completed work when execution pauses or restarts.
The run keeps its state and operating history.
You define the order, retry policy, failure handling, and review points. Swirls executes that definition and records the path the work took.
Example: Employee onboarding can wait for a start date, retry account setup, and pause for equipment approval without turning the process into scattered jobs and callbacks.
Swirls owns the production work behind it.
Durable execution, declared retries, authorized review pauses, and run history.
Wait
Pause for time, an event, or a person without losing state.
Recover
Apply declared retry policy without repeating completed work.
Explain
Inspect where the run stopped and which source defined it.
- Events and schedules
- Waits and retries
- Human review
- Failure handling
- Run history
You own
The sequence, business rules, exceptions, approvals, and definition of done.
Define the process that cannot lose its place.
Name the steps, waits, failure policy, and human decisions. Let the runtime carry the state.