Skip to content

Note on sustained payloads at 2MB limit #4712

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
lennessyy merged 2 commits into from
Jun 23, 2026
+8 −0
Merged

Note on sustained payloads at 2MB limit #4712

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a0d7504
Note on sustained payloads at 2MB limit
jpvotta Jun 12, 2026
a2bf117
Merge branch 'main' into docs/large-payload-rate-limit-note
lennessyy Jun 23, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions docs/evaluate/temporal-cloud/limits.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

@lennessyy lennessyy Jun 23, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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?

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:
Expand Down