Clarify throttling behavior when exceeding APS limits#4161
Merged
brianmacdonald-temporal merged 6 commits intomainfrom Feb 4, 2026
Merged
Clarify throttling behavior when exceeding APS limits#4161brianmacdonald-temporal merged 6 commits intomainfrom
brianmacdonald-temporal merged 6 commits intomainfrom
Conversation
Add detailed documentation about what actually happens when Namespace rate limits are exceeded, based on community feedback. Key clarifications: - Priority-based throttling (low-priority ops throttled first) - Burst tolerance allows temporary spikes - ResourceExhausted errors and SDK retry behavior - Calls CAN fail if throttling persists beyond retry limits - Best practices for handling throttling This corrects the previous implication that "work is never lost" which was misleading - client calls can fail if not handled properly. Co-Authored-By: Claude Opus 4.5 <[email protected]>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
📖 Docs PR preview links
|
- Move throttling behavior section above schedules rate limit - Add link to OSS throttling priorities (quotas.go) - Link from capacity-modes to limits#throttling-behavior Co-Authored-By: Claude Opus 4.5 <[email protected]>
bechols
requested review from
sergeybykov,
tlotemporal,
tsurdilo and
tusharroy25
- capacity-modes.mdx: Change bullet point from "burst factor" to describe rate limiting latency - limits.mdx: Rename "Burst tolerance" to "Throttling latency" and update description Co-Authored-By: Claude Opus 4.5 <[email protected]>
brianmacdonald-temporal
approved these changes
Feb 4, 2026
Contributor
brianmacdonald-temporal
left a comment
brianmacdonald-temporal
left a comment
There was a problem hiding this comment.
Good explanation. Thanks!
brianmacdonald-temporal
deleted the
docs/throttling-behavior-clarification
branch
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
2 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.
Summary
Why
A user in the community Slack asked what happens when they hit their APS limit: https://temporalio.slack.com/archives/C04S80QKB2Q/p1769633842536299
The existing docs implied "work is never lost" but this is misleading. Per Tihomir's response in the thread:
Test plan
#throttling-behavioranchor, metrics reference link)🤖 Generated with Claude Code