<config>

<config> defines durable runtime policy for one workflow.

Why use it

Use it when a workflow must limit active runs, control first-start rate, enforce a total deadline, or share a durable FIFO scheduling lane.

Common use cases

• Protect a downstream service with a concurrency cap.
• Apply a strict rolling-window start rate.
• Set a workflow deadline.
• Place related runs on a named scheduling lane.

Syntax

<config
  concurrency="4"
  rate-limit="100/1m"
  timeout="10m"
  queue="orders"
/>

Rules and behavior

• It is optional, self-closing, singleton, and must contain at least one attribute.
• concurrency is a positive integer up to 1,000,000.
• rate-limit uses count/duration.
• timeout ranges from 1ms through 365d.
• queue is a lowercase dot, underscore, or kebab name up to 128 characters.
• Queue time is excluded from the deadline; retries, approvals, child waits, and lifecycle finalization after execution starts are included.

Related documentation

• Workflow structure
• Runtime configuration