temporalio / temporalio/temporal
Workflow Update causing WFT Failure with `Premature end of stream`
Open
Nobody has claimed this yet.
potential-bug
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Expected Behavior
Expect no Workflow Task failure.
Actual Behavior
- There is WF Task failure
- We know this is a transient and benign error, subsequent WFT fetches entire history and resumes well
- Monitoring on Workflow Task Failures causing alerts at Workers
Steps to Reproduce the Problem
- Updates sent to Worfklows in cache after some time (approx. 3 hours)
Specifications
- Version: latest 1.27.2
- Platform:
Contributor guide
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 reproducing the Workflow Task failure after updates are sent to cached Workflows for approximately three hours, using Temporal 1.27.2 and observing the Premature end of stream error. Trace the Workflow Task fetch and history-resume path to determine why this transient condition is reported as a failure; done means the benign condition no longer causes the reported failure or worker monitoring alert.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100