temporalio / temporalio/features
Allow listing and filtering workflows based on current failures.
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.
When performing a batch operation such as a reset or pause, I'd like to be able to query for workflows that are failing and in which their failure fits a certain failure pattern, for example they might have a non-determinism error or have a certain stuck activity.
Describe the solution you'd like
Perhaps you could write a search attribute when certain conditions are met, such as > N retries of an activity or task failure, or when the workflow has been stuck for a certain amount of time.
You could write some key information (e.g. of the activity type that's failing and the class of the error) or a hash of that information, to allow people to narrow their queries.
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
No files, tests, or implementation entry points are identified in the issue. Start by clarifying the workflow failure conditions, search-attribute behavior, and SDK or Core scope; done would include an agreed queryable design and corresponding per-SDK tickets or tests.
Written by the indexing model from the issue text.
Assessment
- Domain
- distributed-systems, search
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100