Note on sustained payloads at 2MB limit#4712
Merged
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
📖 Docs PR preview links
|
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) <noreply@anthropic.com>
jpvotta
force-pushed
the
docs/large-payload-rate-limit-note
branch
from
8692214 to
a0d7504
Compare
lennessyy
approved these changes
Jun 23, 2026
lennessyy
reviewed
Jun 23, 2026
| :::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. |
Contributor
There was a problem hiding this comment.
Suggested change
| 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. | |
| Sustained, high-volume use of large payloads can degrade Namespace performance, and we may rate limit such traffic to protect the service. |
I personally feel like "Temporal reserves the right to" sounds a bit aggressive, kind of like we are about to sue them. Making this a little more direct actually sounds softer?
bechols
approved these changes
Jun 23, 2026
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
Adds a note to the Transaction Payload size limit section of the Temporal Cloud limits page clarifying 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 to protect the service. Points readers to External Storage for workloads that regularly produce large payloads.
Why
Customers have read the documented 2 MB payload limit as a guarantee that sustained, high-volume 2 MB payloads will be served at scale. In practice, sustained large-payload traffic can degrade Namespace performance even though any single request is within limits.
Changes
docs/evaluate/temporal-cloud/limits.mdx: added a:::noteafter the 2 MB limit statement.┆Attachments: EDU-6531 Note on sustained payloads at 2MB limit