You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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 -
The text was updated successfully, but these errors were encountered:
Visibility into workflows that have task failures or are otherwise stuck is a good/common request, but I think it's a server issue (at least at first). At the least you may want an issue at https://github.com/temporalio/temporal and link to it from here if it does not already exist.
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
The text was updated successfully, but these errors were encountered: