[GH-ISSUE #220] [QUESTION] Is it possible to move a job from one queue to another? #76

Closed
opened 2026-03-02 05:18:28 +03:00 by kerem · 1 comment
Owner

Originally created by @sujit-baniya on GitHub (Jan 3, 2021).
Original GitHub issue: https://github.com/hibiken/asynq/issues/220

Originally assigned to: @hibiken on GitHub.

Is it possible to move a job from one queue to another queue?

Use-Case:
Sometime user has to be moved from low priority to high priority queue.

Originally created by @sujit-baniya on GitHub (Jan 3, 2021). Original GitHub issue: https://github.com/hibiken/asynq/issues/220 Originally assigned to: @hibiken on GitHub. Is it possible to move a job from one queue to another queue? Use-Case: Sometime user has to be moved from low priority to high priority queue.
kerem 2026-03-02 05:18:28 +03:00
Author
Owner

@hibiken commented on GitHub (Jan 5, 2021):

Hi @sujit-baniya! Thank you for the question.

The move operation you described above is not supported currently. Once a task is put into a queue, it's stuck with that queue. This is mostly due to the fact that we use the queue name string for the hash tag for redis cluster.

A workaround would be to delete the task from the source queue and enqueue a new task to the destination queue to do a "move" operation (one downside is that this operation won't be an atomic one)

I'll close this issue since I don't see supporting this feature

<!-- gh-comment-id:754395505 --> @hibiken commented on GitHub (Jan 5, 2021): Hi @sujit-baniya! Thank you for the question. The move operation you described above is not supported currently. Once a task is put into a queue, it's stuck with that queue. This is mostly due to the fact that we use the queue name string for the hash tag for redis cluster. A workaround would be to delete the task from the source queue and enqueue a new task to the destination queue to do a "move" operation (one downside is that this operation won't be an atomic one) I'll close this issue since I don't see supporting this feature
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#76
No description provided.