From a0d7504bdd9a2731111cb1bb4feff6d44a7e87e4 Mon Sep 17 00:00:00 2001 From: John Votta Date: Fri, 12 Jun 2026 15:37:36 -0700 Subject: [PATCH] Note on sustained payloads at 2MB limit Clarify that the 2 MB payload limit is a per-request maximum, not a sustained-throughput target, and that Temporal reserves the right to rate limit high-volume large-payload traffic. Point readers to External Storage for workloads that regularly produce large payloads. Co-Authored-By: Claude Opus 4.8 (1M context) --- docs/evaluate/temporal-cloud/limits.mdx | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/docs/evaluate/temporal-cloud/limits.mdx b/docs/evaluate/temporal-cloud/limits.mdx index 1a2c1f140b..cf4acec25a 100644 --- a/docs/evaluate/temporal-cloud/limits.mdx +++ b/docs/evaluate/temporal-cloud/limits.mdx @@ -237,6 +237,14 @@ This limit is non-configurable for Temporal Cloud. The [BlobSizeLimitError guide](/troubleshooting/blob-size-limit-error) provides solutions for handling large payloads. +:::note + +The 2 MB limit is the maximum size for a single request, not a sustained-throughput target. +Sustained, high-volume use of large payloads can degrade Namespace performance, and Temporal reserves the right to rate limit such traffic to protect the service. +For workloads that regularly produce large payloads, offload them to [External Storage](/external-storage) and keep inline payloads small. + +::: + ### Per Workflow Execution concurrency limits If a Workflow Execution has 2,000 incomplete Activities, Signals, Child Workflows, or external Workflow Cancellation requests, additional [Commands](/workflow-execution#command) of that type will fail to be applied to that Workflow Execution: