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
{{ message }}
This repository has been archived by the owner on Sep 30, 2024. It is now read-only.
@mrnugget Just thought of this: this should probably be a presentation concern in either the UI or the GraphQL layer. We can add convenience methods to help (e.g. record.WouldRetry()), though.
The data we need is already there the record (our num resets) and in the max retires constant. When presenting the error message, simply prepend retries exhausted. won't retry. previous error: (or similar) to the last failure. This won't totally erase the error conditions (which I think should still be available somehow to aid in debugging the reason it failed so many times in the first place).
It would be nice if the worker would log in
failure_message
when all retries have been exhausted.Right now the
num_resets
column is bumped when a record is dequeued on retry. So, in pseudo-code, we could do something like this:The text was updated successfully, but these errors were encountered: