temporalio / temporalio/features
GetWorkflowHistory payload size exceeds limit for a single page
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 32
- Forks
- 28
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 7
Description
Is your feature request related to a problem? Please describe.
A workflow page with large payloads can exceed the GRPC limit.
For example, a user might have a proxy that has a 4MB limit and when downloading a page of history with GetWorkflowHistory that has large payloads in it (such as activity args), it could be larger than that limit.
This gets the workflow into a state that's difficult-to-impossible to recover from.
Describe the solution you'd like
Dunno. Try pagination through smaller pages if there's a size problem? Implement a payload store?
Additional context
Per-SDK Tickets
- Go -
- Java -
- Core -
- TypeScript -
- Python -
- .NET -
- PHP -
- Temporal CLI -
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the GetWorkflowHistory API and the stated 4MB proxy-limit scenario. The issue does not identify files, tests, or a chosen solution; first clarify whether smaller pagination or a payload store is intended, then determine the required work across the listed Go, Java, Core, TypeScript, Python, .NET, PHP, and Temporal CLI tickets.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- grpc
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100