Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Api Error Job {...} does not exist should not count as a fault for the purpose of _consecutive_failed_jobs #255

Open
tazlin opened this issue Aug 15, 2024 · 0 comments
Open

Api Error Job {...} does not exist should not count as a fault for the purpose of _consecutive_failed_jobs #255

tazlin opened this issue Aug 15, 2024 · 0 comments
Labels
bug Something isn't working good first issue Good for newcomers

Comments

@tazlin
Copy link
Member

tazlin commented Aug 15, 2024

By incrementing ._consecutive_failed_jobs for this error, the worker will erroneously pause popping jobs. As this error does not indicate poor conditions on the worker (and is in fact a race-condition API-side to do with the database) it is incorrect to consider this error a form of fault/failed job.
@tazlin tazlin mentioned this issue Aug 15, 2024
Closed
@tazlin tazlin changed the title Api Error Too many consecutive failed jobs should not count as a fault for the purpose of _consecutive_failed_jobs Api Error Job {...} does not exist should not count as a fault for the purpose of _consecutive_failed_jobs Aug 16, 2024
@tazlin tazlin added bug Something isn't working good first issue Good for newcomers labels Jan 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working good first issue Good for newcomers
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@tazlin