From 8b26371b086fadf237a9649956a4da623d437c86 Mon Sep 17 00:00:00 2001 From: John Votta Date: Wed, 15 Jul 2026 08:16:52 -0700 Subject: [PATCH] Clarify Support-set APS limit is preserved across capacity mode switches Co-Authored-By: Claude Opus 4.8 (1M context) --- docs/best-practices/managing-aps-limits.mdx | 1 + docs/cloud/capacity-modes.mdx | 6 +++++- 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/docs/best-practices/managing-aps-limits.mdx b/docs/best-practices/managing-aps-limits.mdx index 0c323d0fb1..bd18825f89 100644 --- a/docs/best-practices/managing-aps-limits.mdx +++ b/docs/best-practices/managing-aps-limits.mdx @@ -207,6 +207,7 @@ Use Provisioned capacity when the on-demand model can't respond quickly enough: :::note When switching back to on-demand mode, your APS limit resets to the running average from the last 7 days. +If Temporal Support has set a custom limit for your Namespace, that limit is preserved across the switch. Plan for this if your workload is sensitive to the transition. ::: diff --git a/docs/cloud/capacity-modes.mdx b/docs/cloud/capacity-modes.mdx index 28cf56d21c..26e684bb9d 100644 --- a/docs/cloud/capacity-modes.mdx +++ b/docs/cloud/capacity-modes.mdx @@ -100,7 +100,7 @@ Actions that are external to the core Temporal service do not contribute to your ## On-Demand Capacity {/* #on-demand-capacity */} Using On-Demand Capacity, your rate limit grows automatically along with your usage. -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). +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. Scaling automatically adjusts based on the lesser of 4 * APS Average or 2 * APS P90 over the past 7 days. @@ -180,6 +180,10 @@ For the metrics to watch and how to alert on utilization, see [Provisioned capac Capacity Modes and TRUs can be set via the Temporal Cloud UI, CLI, or API. Capacity modes can be set and adjusted by Global Admin and Namespace Admin. +When you switch to Provisioned Capacity, your limit is set by the number of TRUs you select. +When you switch back to On-Demand, your limit is recalculated from the trailing 7-day usage formula and never falls below your floor. +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. + ### Setting Capacity Modes from the UI 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/`).