[GH-ISSUE #1053] [BUG] recoverer: could not move task to archive: INTERNAL_ERROR: redis eval error: NOT FOUND — Unexpected Warning with Redis Sentinel #2529

Open
opened 2026-03-15 20:47:56 +03:00 by kerem · 2 comments
Owner

Originally created by @htnphu on GitHub (May 27, 2025).
Original GitHub issue: https://github.com/hibiken/asynq/issues/1053

Originally assigned to: @hibiken, @kamikazechaser on GitHub.

Describe the bug
Hi everyone,

I'm encountering the following recurring warning when using Asynq v0.25.1 with Redis Sentinel:
recoverer: could not move task to archive: INTERNAL_ERROR: redis eval error: NOT FOUND
recoverer: could not retry lease expired task: INTERNAL_ERROR: redis eval error: NOT FOUND

I understand this message typically indicates a task is missing from Redis when the recoverer tries to archive it, but in my case, I’ve not deleted any task keys manually.

Environment :

  • Redis version: v9.7.0
  • Redis mode: Sentinel setup (with failover)
  • Asynq version: v0.25.1
  • No manual deletion of Redis keys has been done.
  • Tasks are processed normally, but this warning appears periodically.
Originally created by @htnphu on GitHub (May 27, 2025). Original GitHub issue: https://github.com/hibiken/asynq/issues/1053 Originally assigned to: @hibiken, @kamikazechaser on GitHub. **Describe the bug** Hi everyone, I'm encountering the following recurring warning when using Asynq v0.25.1 with Redis Sentinel: `recoverer: could not move task to archive: INTERNAL_ERROR: redis eval error: NOT FOUND` `recoverer: could not retry lease expired task: INTERNAL_ERROR: redis eval error: NOT FOUND` I understand this message typically indicates a task is missing from Redis when the recoverer tries to archive it, but in my case, I’ve not deleted any task keys manually. **Environment :** - `Redis` version: v9.7.0 - Redis mode: Sentinel setup (with failover) - `Asynq` version: v0.25.1 - No manual deletion of Redis keys has been done. - Tasks are processed normally, but this warning appears periodically.
Author
Owner

@jeffphp commented on GitHub (Dec 9, 2025):

In case it helps: https://github.com/hibiken/asynq/issues/764#issuecomment-3611269765

<!-- gh-comment-id:3630901673 --> @jeffphp commented on GitHub (Dec 9, 2025): In case it helps: https://github.com/hibiken/asynq/issues/764#issuecomment-3611269765
Author
Owner

@htnphu commented on GitHub (Dec 9, 2025):

Thank you so much @jeffphp !! I'll take a look at it

<!-- gh-comment-id:3631008588 --> @htnphu commented on GitHub (Dec 9, 2025): Thank you so much @jeffphp !! I'll take a look at it
Sign in to join this conversation.
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#2529
No description provided.