Expose poller error on max deployments instead of masking it as internal #8785
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What changed?
Expose poller error on max deployments instead of masking it as internal
Why?
Users should see this. https://temporaltechnologies.slack.com/archives/C02LGH6BG3A/p1764816658963239
How did you test it?
Potential risks
Any change is risky. Identify all risks you are aware of. If none, remove this section.
Note
Surfaces the "too many worker deployments in namespace" error to pollers and standardizes the error message used when the max deployments limit is exceeded.
workerdeployment.ErrTooManyDeploymentsInNamespacePrefix, return it directly instead oferrDeploymentVersionNotReadyinphysical_task_queue_manager.ensureRegisteredInDeploymentVersion.ErrTooManyDeploymentsInNamespacePrefixanderrTooManyDeploymentsInNamespaceinservice/worker/workerdeployment/util.go.client.updateWithStartWorkerDeployment.Written by Cursor Bugbot for commit 4f9a8ba. This will update automatically on new commits. Configure here.