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
This isn't a que-web bug per se, but it is a bit confusing. If a job's error_count has exceeded max_retry_count and expired_at has a value, this job is effectively "dead" and yet que-web allows you to retry it, and gives the impression that it has been retried (run_at updates) - yet the job is not actually re-run. I don't know if there's a way around this, though I've opened an issue with que to find out - if so, we should fix in que-web, otherwise add some logic to disable the retry button for such jobs.
The text was updated successfully, but these errors were encountered:
I'm onboard with having the ability to retry expired jobs. Would give a way to manually deal with dead jobs beyond deleting.
Maybe setting expired_at=NULL on retry would be enough given the :poll_jobs SQL doesn't pay any attention to error_count, it only looks for expired_at IS NULL.
This isn't a que-web bug per se, but it is a bit confusing. If a job's
error_count
has exceededmax_retry_count
andexpired_at
has a value, this job is effectively "dead" and yet que-web allows you to retry it, and gives the impression that it has been retried (run_at
updates) - yet the job is not actually re-run. I don't know if there's a way around this, though I've opened an issue with que to find out - if so, we should fix in que-web, otherwise add some logic to disable the retry button for such jobs.The text was updated successfully, but these errors were encountered: