Documentation / Build
Wait without holding a worker
Use durable asynchronous work for long-running tools, external jobs and human approvals.
The flow
- A phase records the dispatch intent and its operation identity.
- The provider accepts the job; the workflow waits durably.
- The provider returns an authenticated callback.
- A valid completion resumes the waiting work.
Use the issued identity
Keep the operation identity, callback credential and ownership epoch together. Reuse the same provider idempotency key when recovering an uncertain dispatch.
Use the originally issued callback credential. Recovery may preserve its issued epoch; the current owner is fenced separately. Do not invent a new token on retry.
Inspect a waiting execution
rippflow executions inspect EXECUTION_ID --json
rippflow executions history EXECUTION_ID --jsonRequires an authenticated installation. Local handler runs do not certify this recovery path.
Verified sources
Checked 2026-11-05.
- Durable dispatch and callback fencing 04cb082 · main
- Asynchronous developer journey 3a3be99 · main
