temporalio / temporalio/temporal
the status remains as "running"
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
When I use Temporal deployed on Alibaba Cloud SAE, there is a situation where the workflow gets stuck, and the status remains as "running". Of course, this happens roughly once in every 100 cases during my batch testing
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 intermittent stuck workflow in a Temporal deployment on Alibaba Cloud SAE using the reported batch-testing scenario. Gather the workflow and service configuration, execution history, and logs for a failed run; done means identifying a repeatable cause and verifying that affected workflows no longer remain in "running".
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, distributed-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100