[GH-ISSUE #26] Re-evaluate retry count semantics #2030

New issue

Closed

opened 2026-03-15 18:51:18 +03:00 by kerem · 1 comment

kerem commented

2026-03-15 18:51:18 +03:00

Owner

Originally created by @hibiken on GitHub (Dec 26, 2019).
Original GitHub issue: https://github.com/hibiken/asynq/issues/26

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.

Originally created by @hibiken on GitHub (Dec 26, 2019). Original GitHub issue: https://github.com/hibiken/asynq/issues/26 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.

kerem closed this issue

2026-03-15 18:51:23 +03:00

kerem commented

2026-03-15 18:51:29 +03:00

Author

Owner

@hibiken commented on GitHub (Jan 23, 2020):

Closing

@hibiken commented on GitHub (Jan 23, 2020): Closing

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/asynq#2030

No description provided.

Rows
Columns