Temporal Workflow Designer

Temporal is a durable execution platform that automatically persists workflow state and retries failed steps. The Workflow Designer focuses on visually composing the step sequence — activities, timers, signals, conditions, parallel fan-outs, and child workflows — and generating the core workflow function code. It shows you the shape of your workflow at a glance before you write any logic.

Activities are the actual work units — calling external APIs, reading from databases, sending emails. They run outside the workflow sandbox and can be retried automatically on failure. Timers (step.sleep / workflow.Sleep) pause execution for a duration without consuming resources. Signals are external messages sent to a running workflow to change its state or unblock a waiting condition — ideal for human-in-the-loop approval flows or order cancellation.

Use parallel steps (Promise.all in TypeScript, asyncio.gather in Python) when multiple activities are independent and can run concurrently — for example, simultaneously sending an email, creating a Slack notification, and logging an audit record. Parallel fan-out dramatically reduces overall workflow duration when activities don't depend on each other's output.

Temporal retries failed Activities automatically with exponential backoff. maximumAttempts sets the ceiling — if all attempts fail, the workflow receives an ApplicationError. The default retry policy retries indefinitely (unlimited attempts) with exponential backoff capped at 100 seconds. Set maximumAttempts to a specific number for non-idempotent operations where retrying would cause duplicate side effects (e.g. charging a credit card).

A Child Workflow is a full Temporal workflow started by a parent workflow. Use child workflows to decompose large workflows into reusable units, to apply different retry/timeout policies to a section of work, or when a sub-process needs its own observable timeline in the Temporal UI. Child workflows run independently and can outlive the parent if configured to. For simple activity grouping without independent observability, use activity sequences instead.

No. All code generation runs entirely in your browser using JavaScript. Your workflow names, activity names, and configuration never leave your machine.