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 a self-hosted Server or Cloud managed runtime.
Negotiate local activities, worker sessions, and sticky execution safely across PHP, Python, and Rust service workers.
The Python SDK is a thin, async-first client for a self-hosted Durable Workflow
Run the shared Sample App Rust playground against a provisioned Durable Workflow Cloud namespace.
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.