[GH-ISSUE #871] Order of task execution #428

New issue

Open

opened 2026-03-02 05:21:08 +03:00 by kerem · 6 comments

kerem commented

2026-03-02 05:21:08 +03:00

Owner

Originally created by @dikdom on GitHub (Apr 25, 2024).
Original GitHub issue: https://github.com/hibiken/asynq/issues/871

Hello,
is there any guarantee of the task execution order depending on the enqueue order?
I know this sounds silly as this is a queue but unfortunately I have some contradicting experience. Shall I continue investigating my setup or there is no guarantee of the order of the task executions?
Thanks!

Originally created by @dikdom on GitHub (Apr 25, 2024). Original GitHub issue: https://github.com/hibiken/asynq/issues/871 Hello, is there any guarantee of the task execution order depending on the enqueue order? I know this sounds silly as this is a queue but unfortunately I have some contradicting experience. Shall I continue investigating my setup or there is no guarantee of the order of the task executions? Thanks!

kerem commented

2026-03-02 05:21:09 +03:00

Author

Owner

@kamikazechaser commented on GitHub (Apr 26, 2024):

Well there are ways to achieve something similar. Forcing lower concurrency, checking previous task status in task handlers. But there are no guarantees in any case.

@kamikazechaser commented on GitHub (Apr 26, 2024): Well there are ways to achieve something similar. Forcing lower concurrency, checking previous task status in task handlers. But there are no guarantees in any case.

kerem commented

2026-03-02 05:21:09 +03:00

Author

Owner

@dikdom commented on GitHub (Apr 29, 2024):

That is sad, I mean this is meant to be a queue. In theory when there is only one process that executes the tasks, then the order of the executions should be the same order as they were inserted in the queue. Am I missing here something?

@dikdom commented on GitHub (Apr 29, 2024): That is sad, I mean this is meant to be a queue. In theory when there is only one process that executes the tasks, then the order of the executions _should be_ the same order as they were inserted in the queue. Am I missing here something?

kerem commented

2026-03-02 05:21:09 +03:00

Author

Owner

@Joker666 commented on GitHub (Oct 11, 2024):

@dikdom what you are looking for is called a workflow. Asynq does not support that. Try River Pro, it supports workflows.

@Joker666 commented on GitHub (Oct 11, 2024): @dikdom what you are looking for is called a workflow. `Asynq` does not support that. Try River Pro, it supports workflows.

kerem commented

2026-03-02 05:21:09 +03:00

Author

Owner

@sanudatta11 commented on GitHub (Oct 25, 2024):

what you generally want is kind of like a state machine inside a queue handler

@sanudatta11 commented on GitHub (Oct 25, 2024): what you generally want is kind of like a state machine inside a queue handler

kerem commented

2026-03-02 05:21:09 +03:00

Author

Owner

@kamikazechaser commented on GitHub (Oct 26, 2024):

https://github.com/yuyang0/dagflow

@kamikazechaser commented on GitHub (Oct 26, 2024): https://github.com/yuyang0/dagflow

kerem commented

2026-03-02 05:21:09 +03:00

Author

Owner

@PterX commented on GitHub (Jan 17, 2025):

I had a similar need, and I finally implemented it in a simple way. I created an asynq middleware to maintain a dependency relationship of task type. In the middle, it records whether all the dependent tasks have been executed. Otherwise, the dependent tasks will be requeued until they are depended on. All tasks have been completed

@PterX commented on GitHub (Jan 17, 2025): I had a similar need, and I finally implemented it in a simple way. I created an asynq middleware to maintain a dependency relationship of task type. In the middle, it records whether all the dependent tasks have been executed. Otherwise, the dependent tasks will be requeued until they are depended on. All tasks have been completed