Eager Workflow Start requires server-side dynamic config flag enablement

info

configurationUpdated Mar 3, 2026

EWS must be enabled at the server level using the dynamic configuration flag system.enableEagerWorkflowStart. For Temporal Cloud, this requires opening a support ticket.

Sources

Improving latency with Eager Workflow Start in Temporaltemporal.io

Technologies:

Temporalsubject

How to detect:

The server must have system.enableEagerWorkflowStart set to true in dynamic configuration for EWS to function.

Recommended action:

1. For local development with temporal server start-dev, add flag: --dynamic-config-value system.enableEagerWorkflowStart=true. 2. For self-hosted Temporal Server, update dynamic configuration to set system.enableEagerWorkflowStart=true. 3. For Temporal Cloud, open a support ticket to request EWS enablement for your namespace. 4. Verify flag is enabled before deploying client-side EWS configuration. 5. Test in non-production environment first to validate behavior.