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

shell
rippflow executions inspect EXECUTION_ID --json
rippflow executions history EXECUTION_ID --json

Requires an authenticated installation. Local handler runs do not certify this recovery path.

Verified sources

Checked 2026-11-05.

Let's talk

Contact Rippflow

Tell us about your workflows, deployment or pricing.

We'll reply to your email.

Search docs

Search workflows, handlers and operations.