Configure wait state tracking

Configure wait state tracking in Camunda 8 Self-Managed.

Enable or disable wait state tracking

Wait state tracking is enabled by default. You can disable it if you do not want to track this data.

To change the default behavior in Camunda 8 Self-Managed, configure your deployment:

Application properties

camunda:
  data:
    wait-states:
      enabled: true # Wait state tracking is enabled by default

Environment variables

CAMUNDA_DATA_WAITSTATES_ENABLED=true

Helm

orchestration:
  extraConfiguration:
    - file: additional-spring-properties.yaml
      content: |
        camunda:
          data:
            wait-states:
              enabled: true # Wait state tracking is enabled by default

See all configuration options to learn more.

Disabling wait state tracking stops new wait states from being tracked. It doesn't purge existing wait state data immediately. The secondary storage retention settings clean up that data over time. Until the data is cleaned up, you can continue to access it in Operate and the Search API.

Configure secondary storage retention

With Camunda 8 Self-Managed, you control the secondary storage retention policy, which applies to wait state records:

Application properties

camunda:
  data:
    secondary-storage:
      retention:
        enabled: true
        minimum-age: 30d

Environment variables

CAMUNDA_DATA_SECONDARYSTORAGE_RETENTION_ENABLED=true
CAMUNDA_DATA_SECONDARYSTORAGE_RETENTION_MINIMUMAGE=30d

Helm

orchestration:
  retention:
    enabled: true
    minimumAge: 30d

See Configure data retention for more information about the Helm configuration.