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.
We would like to show the status of a job in our UI when failed/completed, without being sensitive to the number of retries. It's difficult to distinguish a failed job (that is going to retry) vs. a failed job that has exhausted its retries using the Job API. It seems like the status of retries being exhausted is only available via QueueEvents.
Describe the solution you'd like
A field on Job like retriesLeft or retriesExhausted that can be polled to see if the job is going to retry on failure.
Describe alternatives you've considered
Using the QueueEvents API to return the retry status to the UI is more complicated, and does not mix well with polling for job status.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
We would like to show the status of a job in our UI when failed/completed, without being sensitive to the number of retries. It's difficult to distinguish a failed job (that is going to retry) vs. a failed job that has exhausted its retries using the Job API. It seems like the status of retries being exhausted is only available via QueueEvents.
Describe the solution you'd like
A field on
Job
likeretriesLeft
orretriesExhausted
that can be polled to see if the job is going to retry on failure.Describe alternatives you've considered
Using the QueueEvents API to return the retry status to the UI is more complicated, and does not mix well with polling for job status.
The text was updated successfully, but these errors were encountered: