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

Re-evaluate retry count semantics #26

Closed
hibiken opened this issue Dec 26, 2019 · 1 comment
Closed

Re-evaluate retry count semantics #26

hibiken opened this issue Dec 26, 2019 · 1 comment

Comments

@hibiken
Copy link
Owner

hibiken commented Dec 26, 2019

Currently we increment Retried field on TaskMessage when we move the task to retry queue. This data is visible to user via asynqmon and user will see Retried 1 after first attempt to process the task fails. This could be confusing to user since the task is scheduled for a retry but hasn't been retried yet.
@hibiken
Copy link
Owner Author

hibiken commented Jan 23, 2020

Closing

@hibiken hibiken closed this as completed Jan 23, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@hibiken