Skip to content

Document the per-Namespace Worker Controller Instance limit - #33

Open
temporal-plugin-updater[bot] wants to merge 1 commit into
mainfrom
skill-sync/2026-10-27-skill-sync-issue-148-928015a-0003
Open

temporal-plugin-updater[bot] wants to merge 1 commit into
mainfrom
skill-sync/2026-10-27-skill-sync-issue-148-928015a-0003

Conversation

@temporal-plugin-updater

Copy link
Copy Markdown
Contributor

Agents can now explain and work around the default limit of 100 Worker Controller Instances per Namespace. references/wci.md covers which versions count (every version with a compute configuration, including drained ones, across all Worker Deployments), the reached maximum worker controller instances in namespace error, deleting versions to free room, and contacting support on Temporal Cloud. Both providers' self-hosted references add the workercontroller.maxInstances dynamic config key, which can be scoped to one Namespace with constraints.

Upstream sources:

Draft eval PR: https://github.com/temporalio/skill-evals/pull/468

… how to make room, how to raise it on Cloud and self-hosted) to references/wci.md, and add the `workercontroller.maxInstances` dynamic config key to both providers' self-hosted references.
@temporal-plugin-updater
temporal-plugin-updater Bot marked this pull request as ready for review November 19, 2026 02:31
@temporal-plugin-updater
temporal-plugin-updater Bot requested a review from a team as a code owner November 19, 2026 02:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants