Set poller autoscaling namespace capability#9572
Merged
Conversation
Set the PollerAutoscaling namespace capability unconditionally to true, so SDKs know the server supports poller scaling decisions and can safely scale down pollers on empty responses. Made-with: Cursor
rkannan82
force-pushed
the
kannan/poller-autoscaling-capability
branch
from
a6d6837 to
d2d3be0
Compare
Sushisource
reviewed
Mar 18, 2026
rkannan82
force-pushed
the
kannan/poller-autoscaling-capability
branch
from
6229a8e to
f34a863
Compare
Made-with: Cursor
rkannan82
force-pushed
the
kannan/poller-autoscaling-capability
branch
from
f34a863 to
f38867c
Compare
ShahabT
approved these changes
Mar 19, 2026
stephanos
pushed a commit
that referenced
this pull request
Mar 20, 2026
Set the `PollerAutoscaling` namespace capability unconditionally to `true`. This new capability was introduced in temporalio/api#723. SDKs need to know the server supports poller scaling decisions so they can safely scale down pollers on empty responses. Without this capability, SDKs can't be sure the server would ever tell them to scale back up (if the server is old). Poller autoscaling is enabled/disabled on the worker (SDK) side — the server always supports sending scaling decisions, so this capability is hardcoded to `true`. - [x] built - [x] covered by existing tests (`TestCapabilitiesAndLimits`) None — additive capability flag, no behavioral change on the server. Made with [Cursor](https://cursor.com)
This was referenced Mar 21, 2026
birme
pushed a commit
to eyevinn-osaas/temporal
that referenced
this pull request
Mar 23, 2026
## What changed? Set the `PollerAutoscaling` namespace capability unconditionally to `true`. This new capability was introduced in temporalio/api#723. ## Why? SDKs need to know the server supports poller scaling decisions so they can safely scale down pollers on empty responses. Without this capability, SDKs can't be sure the server would ever tell them to scale back up (if the server is old). Poller autoscaling is enabled/disabled on the worker (SDK) side — the server always supports sending scaling decisions, so this capability is hardcoded to `true`. ## How did you test it? - [x] built - [x] covered by existing tests (`TestCapabilitiesAndLimits`) ## Potential risks None — additive capability flag, no behavioral change on the server. Made with [Cursor](https://cursor.com)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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?
Set the
PollerAutoscalingnamespace capability unconditionally totrue. This new capability was introduced in temporalio/api#723.Why?
SDKs need to know the server supports poller scaling decisions so they can safely scale down pollers on empty responses. Without this capability, SDKs can't be sure the server would ever tell them to scale back up (if the server is old).
Poller autoscaling is enabled/disabled on the worker (SDK) side — the server always supports sending scaling decisions, so this capability is hardcoded to
true.How did you test it?
TestCapabilitiesAndLimits)Potential risks
None — additive capability flag, no behavioral change on the server.
Made with Cursor