Skip to content

Commit 3f26bd7

Browse files
jpvottaclaude
andauthored
Clarify Support-set APS limit is preserved across capacity mode switches (#4885)
Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
1 parent 9279218 commit 3f26bd7

2 files changed

Lines changed: 6 additions & 1 deletion

File tree

docs/best-practices/managing-aps-limits.mdx

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -207,6 +207,7 @@ Use Provisioned capacity when the on-demand model can't respond quickly enough:
207207

208208
:::note
209209
When switching back to on-demand mode, your APS limit resets to the running average from the last 7 days.
210+
If Temporal Support has set a custom limit for your Namespace, that limit is preserved across the switch.
210211
Plan for this if your workload is sensitive to the transition.
211212
:::
212213

docs/cloud/capacity-modes.mdx

Lines changed: 5 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -100,7 +100,7 @@ Actions that are external to the core Temporal service do not contribute to your
100100
## On-Demand Capacity {/* #on-demand-capacity */}
101101

102102
Using On-Demand Capacity, your rate limit grows automatically along with your usage.
103-
Each Namespace has an Actions per second (APS), Requests per second (RPS), and Operations per second (OPS) limit that scales automatically with usage. Your APS limit never falls below its [default limit](/cloud/limits#actions-per-second).
103+
Each Namespace has an Actions per second (APS), Requests per second (RPS), and Operations per second (OPS) limit that scales automatically with usage. Your APS limit never falls below its [default limit](/cloud/limits#actions-per-second). If Temporal Support has manually set your Namespace's limit, that value becomes your floor in place of the default, and it persists across capacity mode changes.
104104

105105
Scaling automatically adjusts based on the lesser of 4 * APS Average or 2 * APS P90 over the past 7 days.
106106

@@ -180,6 +180,10 @@ For the metrics to watch and how to alert on utilization, see [Provisioned capac
180180
Capacity Modes and TRUs can be set via the Temporal Cloud UI, CLI, or API.
181181
Capacity modes can be set and adjusted by Global Admin and Namespace Admin.
182182

183+
When you switch to Provisioned Capacity, your limit is set by the number of TRUs you select.
184+
When you switch back to On-Demand, your limit is recalculated from the trailing 7-day usage formula and never falls below your floor.
185+
If Temporal Support has set a custom limit for your Namespace, that limit is your floor, so switching to Provisioned and back to On-Demand preserves it.
186+
183187
### Setting Capacity Modes from the UI
184188

185189
You can set Capacity Modes for an individual Namespace by navigating to the Namespace page in the Temporal Cloud UI (`https://cloud.temporal.io/namespaces/<Namespace ID>`).

0 commit comments

Comments
 (0)