Activity Execution Model
How ordinary queued activities, local activities, worker sessions, and sticky execution fit together in Durable Workflow v2.
How ordinary queued activities, local activities, worker sessions, and sticky execution fit together in Durable Workflow v2.
Run short activity work inside the current workflow worker process while preserving durable activity history, retries, timeouts, and visibility.
Connect framework-neutral PHP applications and remote workers to the standalone Durable Workflow server.
The Python SDK is a thin, async-first client for the Durable Workflow server. It lets Python processes start, observe, signal, and cancel workflows through the server's control-plane API, and register as workers that execute workflow tasks and activities.
Install the first-party Rust SDK and find its crate, source, and generated API documentation.
Interpret the /api/cluster/info topology manifest for Durable Workflow server roles, scaling boundaries, failure domains, and migration steps.
Choose queue routing, local activities, or worker sessions without treating a queue name as physical-host affinity.
Pin a sequence of durable activity attempts to one worker-session lease for GPU, filesystem, or process-local state affinity.