This page addresses the default limits of the Temporal Cloud system. Reach out to your account team should you have any quesitons about these limits.
These limits fall into the following three main categories:
The following aspects apply at the Temporal Cloud Account level (per account).
How many users can I add?
300 users across all Namespaces.
How many namespaces can I create?
By default, each account is provisioned with ten Namespaces. As you create and use your Namespaces, for example by scheduling Workflows, Temporal Cloud automatically raises your limit. Our service identifies your usage patterns. It responds by slowly increasing your allowance, up to 100 Namespaces. You can request further increases beyond the 100 Namespace limit by opening a support ticket.
Retained Prometheus endpoint data
How much metrics data does the Prometheus endpoint retain?
The Prometheus endpoint retains 30 days of data.
Supported operators in List Filters
Which operators aren't supported in Temporal Cloud?
ORDER BY operator isn't supported in List Filters in Temporal Cloud.
This means that custom ordering of Workflows with Temporal Cloud Visibility isn't possible. Lists of Workflows are still ordered by a default ordering rule, but be aware that this rule might change.
The following aspects apply at the Namespace level (per Namespace).
What is the limit of Actions per second?
Each Namespace has a rate limit, which is measured in Actions per second (APS). A Namespace may be throttled when its throughput becomes too high. Throttling means limiting the rate at which Actions are performed to prevent the Namespace from exceeding its APS limit. A Namespace's default limit is set at 400 APS and automatically adjusts based on recent usage (over the prior 7 days). Your throughput limit will never fall below this default value.
What are the certificate limits?
Temporal Cloud limits each Namespace to a total of 32 KB or 16 certificates, whichever is reached first.
Concurrent Task pollers
Is there a limit to concurrent Task pollers?
Temporal Cloud limits each Namespace to 2,000 concurrent Task pollers.
Default Retention Period
What is the default Retention Period?
The Retention Period is set per Namespace.
Temporal Cloud sets the default Retention Period to 30 days. This is configurable in the Temporal Web UI.
Navigate to your list of Namespaces, choose the Namespace you want to update, and select edit:
Choose your Namespace and select Edit
Update the Retention Period
You can set the Retention Period between 1 and 90 days.
How many batch jobs can run at a time?
A Namespace can have just one Batch job running at a time.
Number of Custom Search Attributes
How many custom Search Attributes are allowed per Namespace?
There is a limit to the number of custom Search Attributes per attribute type per Namespace:
|Search Attribute type
Custom Search Attribute names
What constraints are there for Custom Search Attribute names in Temporal Cloud?
When creating custom Search Attributes in Temporal Cloud, the attribute names must adhere to the following constraints:
- Maximum characters: 64
- Allowed characters:
For more information on custom Search Attributes see Custom Search Attributes limits.
Visibility API Rate Limit
What is the rate limit for requests to the Visibility APIs?
The default rate limit for requests to the Visibility APIs, per Namespace, is 10 requests per second.
Programming model level
The following aspects apply at the programming model level.
Identifier length limit
What is the maximum length for identifiers?
Identifiers such as Workflow Id, Workflow Type, and Task Queue names have a maximum length of 1,000 characters in UTF-8 format.
Per message gRPC limit
What is the gRPC limit for each message received?
Each gRPC message received has a limit of 4 MB. This limit applies to all gRPC endpoints across the Temporal Platform.
Event History transaction size limit
What is the size limit for an Event History transaction?
An Event History transaction encompasses a set of operations such as initiating a new Workflow, scheduling an Activity, processing a Signal, or starting a Child Workflow. These operations create Events that are then logged in the Event History. The default transaction size limit restricts the total size of Events that can be accommodated within a single transaction.
The size limit for any given Event History transaction is 4 MB. This isn't configurable.
Per Workflow Execution concurrency limits
How many incomplete concurrent Actions can a Workflow Execution have?
If a Workflow Execution has 2,000 incomplete Activities, Signals, Child Workflows, or external Workflow Cancellation requests, additional Commands of that type will fail to be applied to that Workflow Execution:
Per Workflow Execution Signal limit
What is the limit on the total number of Signals received per Workflow Execution?
A single Workflow Execution may receive up to 10,000 Signals. After that limit is reached, no more Signals will be processed for that Workflow Execution.