Self-hosted Temporal Cluster defaults

Looking for Temporal Cloud defaults?

See the Temporal Cloud defaults and limits page

This page details many of the defaults coded into the Temporal Platform that can produce errors and warnings. Errors are hard limits that fail when reached. Warnings are soft limits that produce a warning log on the server side.

info

These limits might apply specifically to each Workflow Execution and do not pertain to the entire Temporal Platform or individual Namespaces.

• Identifiers: By default, the maximum length for identifiers (such as Workflow Id, Workflow Type, and Task Queue name) is 1000 characters.
  • This is configurable with the limit.maxIDLength dynamic config variable, set to 255 in this SQL example.
  • The character format is UTF-8.
• gRPC: gRPC has a limit of 4 MB for each message received.
• Event batch size: The DefaultTransactionSizeLimit limit is 4 MB. This is the largest transaction size allowed for the persistence of Event Histories.
• Blob size limit for Payloads (including Workflow context and each Workflow and Activity argument and return value; source):
  • Temporal warns at 256 KB: Blob size exceeds limit.
  • Temporal errors at 2 MB: ErrBlobSizeExceedsLimit: Blob data size exceeds limit.
  • This is configurable with BlobSizeLimitError and BlobSizeLimitWarn, if you know what you are doing.
• History total size limit (leading to a terminated Workflow Execution):
  • Temporal warns at 10 MB: history size exceeds warn limit.
  • Temporal errors at 50 MB: history size exceeds error limit.
  • This is configurable with HistorySizeLimitError and HistorySizeLimitWarn, if you know what you are doing.
• History total count limit (leading to a terminated Workflow Execution):
  • Temporal warns after 10,240 Events: history size exceeds warn limit.
  • Temporal errors after 51,200 Events: history size exceeds error limit.
  • This is configurable with HistoryCountLimitError and HistoryCountLimitWarn, if you know what you are doing.
• Concurrent limit
  • The following Commands are limited:
    • ScheduleActivityTask
    • SignalExternalWorkflowExecution
    • RequestCancelExternalWorkflowExecution
    • StartChildWorkflowExecution
  • These will fail if the concurrent pending count exceeds 2,000. For optimal performance, limit concurrent operations to 500 or fewer. This reduces Workflow's Event History size and decreases the loading time in the Web UI.
  • As of v1.21, the open source Temporal Cluster has a default limit of 2,000 pending Activities, Child Workflows, Signals, or Workflow cancellation requests, but you can override the limits in the dynamic configuration using these variables:
    • limit.numPendingActivities.error
    • limit.numPendingSignals.error
    • limit.numPendingCancelRequests.error
    • limit.numPendingChildExecutions.error
  • By default, Batch jobs are limited to one job at a time.
• Custom Search Attributes limits

For details on dynamic configuration keys, see Dynamic configuration reference.