temporalio / temporalio/temporal
Is there a way to detect when workflow is in a Failed State but is still "Running"
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Is your feature request related to a problem? Please describe.
If I do this https://github.com/temporalio/samples-typescript/compare/main...bijeebuss:samples-typescript:main
and then start the workflow it will show up as "Running" but it's actually in a sort of failed state. It also does this in other cases like when you forget to export the workflow.
Things I tried
- Try/Catch (does not catch the error)
- Custom Logger: All I see in the logs is "workflow started" and "workflow completed" and the meta has no way to detect that it actually failed.
- setting retry: { maximumAttempts: 1 }
when starting the workflow does not cause the workflow to enter an actual "Failed" state
Describe the solution you'd like
A way to detect when a workflow enters a state like this. Maybe it already exists but I can't find anything
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 with the linked samples-typescript comparison and reproduce the workflow-start scenario where an unexported workflow or similar error leaves the workflow Running. Review the observed logs, retry behavior, and workflow state to determine whether a supported detection signal exists; done means the detection mechanism or its absence is clearly established.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, typescript
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100