docs: fix inaccuracies in blob size limit error page#4384
Closed
docs: fix inaccuracies in blob size limit error page#4384
Conversation
Restructure into two sections for the two distinct limits: - Payload size limit (2 MB per payload, server-side) - gRPC message size limit (4 MB per message, transport-level) Fix incorrect claim that gRPC oversized response terminates the Workflow — it actually causes an infinite retry loop. Add documentation for the misleading StartToCloseTimeout symptom when Activity results exceed the gRPC limit. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
📖 Docs PR preview links
|
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
lennessyy
commented
Apr 2, 2026
| --- | ||
|
|
||
| The `BlobSizeLimitError` is an error that occurs when the size of a blob (payloads including Workflow context and each Workflow and Activity argument and return value) exceeds the set limit in Temporal. | ||
| Temporal enforces size limits on the data that passes between the Temporal Client, Workers, and the Temporal Service. There are two distinct limits: a 2 MB limit on individual Payloads enforced by the Temporal Service, and a 4 MB limit on entire gRPC messages enforced by the transport layer. Each produces different error messages and behaviors. |
Contributor
Author
There was a problem hiding this comment.
Suggested change
| Temporal enforces size limits on the data that passes between the Temporal Client, Workers, and the Temporal Service. There are two distinct limits: a 2 MB limit on individual Payloads enforced by the Temporal Service, and a 4 MB limit on entire gRPC messages enforced by the transport layer. Each produces different error messages and behaviors. | |
| Temporal enforces size limits on the data that passes between the Temporal Client, Workers, and the Temporal Service. There are two distinct limits: a 2 MB limit on individual Payloads enforced by the Temporal Service, and a 4 MB limit on entire gRPC messages enforced by the transport layer. Each produces different error messages and behaviors, and requires different solutions. |
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Contributor
Author
|
Superseded by #4379, which now contains all these changes. |
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
1 participant
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.
Summary
StartToCloseTimeoutsymptom when Activity results exceed the gRPC limitBlobSizeLimitErrorfrom the opening since it's not a literal error message users would seeTest plan
🤖 Generated with Claude Code
┆Attachments: EDU-6154 docs: fix inaccuracies in blob size limit error page