[GH-ISSUE #803] [BUG] Can not manually retry invisible archived tasks #2419

New issue

Open

opened 2026-03-15 20:25:20 +03:00 by kerem · 1 comment

kerem commented

2026-03-15 20:25:20 +03:00

Owner

Originally created by @dusty-cjh on GitHub (Jan 11, 2024).
Original GitHub issue: https://github.com/hibiken/asynq/issues/803

Originally assigned to: @hibiken on GitHub.

Describe the bug
When meeting significant task failures, the archived tasks shown in asynq dash is max 9999.
After manually retry: asynq task runall --queue=default --state=archived
The tasks can be seen in dash is successfully retried, and then the archived menu just shows 0,
but other failed tasks exceeding this range isn't shown, and never can be retried manually.
Which incurs cumulated Redis memory growth.

To Reproduce
Massive task failed in short time.
(due to the alibaba 11-12 crashing in my case)

Expected behavior
asynq dash can show the exactly archived tasks, which can be fairly retried manually.
Or can I set the archived max tasks by any parameter?
I saw the fixed value maxArchiveSize=10000, used to trim the exceeded tasks.
but I don't see any method to recover the trimmed tasks.
So, is these requirements plausible:

expose an argument to customize the max archived task numbers.
remedy method to recover and retry the archived tasks.

Screenshots

Environment (please complete the following information):

OS: CentOS 7
Asynq v0.24.0

Additional context
This problem is so basic, if there have any existing solution, or the docs I haven't find, please drop me a link, thank you 🙏

Originally created by @dusty-cjh on GitHub (Jan 11, 2024). Original GitHub issue: https://github.com/hibiken/asynq/issues/803 Originally assigned to: @hibiken on GitHub. **Describe the bug** When meeting significant task failures, the archived tasks shown in `asynq dash` is max 9999. After manually retry: `asynq task runall --queue=default --state=archived ` The tasks can be seen in dash is successfully retried, and then the archived menu just shows 0, but other failed tasks exceeding this range isn't shown, and never can be retried manually. Which incurs cumulated Redis memory growth. **To Reproduce** Massive task failed in short time. (due to the alibaba 11-12 crashing in my case) **Expected behavior** `asynq dash` can show the exactly archived tasks, which can be fairly retried manually. Or can I set the archived max tasks by any parameter? I saw the fixed value `maxArchiveSize=10000`, used to trim the exceeded tasks. but I don't see any method to recover the trimmed tasks. So, is these requirements plausible: 1. expose an argument to customize the max archived task numbers. 2. remedy method to recover and retry the archived tasks. **Screenshots** <img width="1816" alt="image" src="https://github.com/hibiken/asynq/assets/45847340/bc4076dc-8b11-40f9-8104-feaa05e7ed1b"> **Environment (please complete the following information):** - OS: CentOS 7 - Asynq v0.24.0 **Additional context** This problem is so basic, if there have any existing solution, or the docs I haven't find, please drop me a link, thank you 🙏

kerem added the

bug

investigate

labels

2026-03-15 20:25:20 +03:00

kerem commented

2026-03-15 20:25:31 +03:00

Author

Owner

@kamikazechaser commented on GitHub (Jan 28, 2024):

Related to:

@kamikazechaser commented on GitHub (Jan 28, 2024): Related to: * #730 * #441 * #743 * #756

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#2419

No description provided.

Rows
Columns