Replies: 1 comment 2 replies
|
I’m open to adding something like this, but I think it’s worth first understanding the concrete use-case. Right now PGQueuer doesn’t log the payload or headers - only metadata - so a true “retry the same job” flow would require additional work, either by extending the log schema or by having the application provide the payload again. I’m also curious why the existing retry mechanisms aren’t sufficient in your case. PGQueuer already supports automatic retries (including backoff at the executor level and recovery of stalled jobs), so understanding what scenario requires a manual retry after those are exhausted would help shape a clean API. |
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
It would be nice if pgqueuer had an API for manual retry of a failed job, after all retries were exhausted. What do you think?
All reactions