Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions docs/encyclopedia/workers/serverless-workers/index.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -90,6 +90,11 @@ The Worker Controller Instance (WCI) is a system Workflow that scales Serverless
One WCI Workflow runs per Worker Deployment Version that has a compute provider configured. The WCI runs in the same
Namespace as your Worker Deployment.

A Namespace runs at most 100 WCI Workflows by default, which caps how many Worker Deployment Versions in the Namespace
can have a compute provider at once. A version's WCI runs until the version is deleted, so drained versions count
against the limit. See
[Max Worker Controller Instances limits](/cloud/limits#max-worker-controller-instances-limits).
Comment on lines +93 to +96

The WCI adjusts the Worker count based on Task Queue conditions. Sync match failures and Task Queue backlog signal that
more capacity is needed, and the WCI adds Workers by triggering the configured compute provider. It also removes
capacity as work drains. How often the WCI re-evaluates the count, and how it sizes the pool, depends on the compute
Expand Down
10 changes: 10 additions & 0 deletions docs/evaluate/temporal-cloud/limits.mdx
Original file line number Diff line number Diff line change
Expand Up @@ -398,3 +398,13 @@ The maximum number of versions that the server allows to be registered in a sing
### Max Task Queues In Deployment Version limits {/* #max-task-queues-in-deployment-version-limits */}

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📝 [vale] <Temporal.Headings> reported by reviewdog 🐶
'Max Task Queues In Deployment Version limits *****************************************************' should use sentence-style capitalization.


The maximum number of Task Queues that the server allows to be registered in a single Worker Deployment Version. Defaults to 100.

### Max Worker Controller Instances limits {/* #max-worker-controller-instances-limits */}

The maximum number of [Worker Controller Instances](/serverless-workers#worker-controller-instance) that the server allows to run in a single Namespace. Defaults to 100. [Contact support](/cloud/support#support-ticket) to increase it.

This limit applies only to [Serverless Workers](/serverless-workers). Temporal runs one Worker Controller Instance for each Worker Deployment Version that has a compute configuration, and the count covers every Worker Deployment in the Namespace. Drained versions still count, because the Worker Controller Instance runs until the version itself is deleted.

Creating or updating a Worker Deployment Version with a compute configuration past the limit fails with `reached maximum worker controller instances in namespace`. To make room without raising the limit, delete Worker Deployment Versions you no longer need.

This limit is separate from [Max versions in deployment limits](#max-versions-in-deployment-limits), which counts versions within one Worker Deployment rather than Worker Controller Instances across the Namespace.
Original file line number Diff line number Diff line change
Expand Up @@ -742,6 +742,10 @@ provider that points to your Lambda function. The compute configuration tells Te
provider type (`aws-lambda`), the Lambda function ARN, and the IAM role to assume. The deployment name and build ID must
match the values in your Worker code.

A Namespace runs at most 100 Worker Deployment Versions with a compute configuration by default. Creating a version
past that limit fails with `reached maximum worker controller instances in namespace`. See
[Max Worker Controller Instances limits](/cloud/limits#max-worker-controller-instances-limits).

You can create the version using the Temporal UI or the Temporal CLI.

<Tabs groupId="create-version-approach">
Expand Down
Original file line number Diff line number Diff line change
Expand Up @@ -772,6 +772,10 @@ Create a [Worker Deployment Version](/production-deployment/worker-deployments/w
configuration points at your Worker Pool. The compute configuration tells Temporal where the pool lives and which
service account to impersonate to manage it. The deployment name and build ID must match the values in your Worker code.

A Namespace runs at most 100 Worker Deployment Versions with a compute configuration by default. Creating a version
past that limit fails with `reached maximum worker controller instances in namespace`. See
[Max Worker Controller Instances limits](/cloud/limits#max-worker-controller-instances-limits).

<Tabs groupId="create-version-approach">
<TabItem value="ui" label="Temporal Cloud UI">

Expand Down