Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Order of task execution #871

Open
dikdom opened this issue Apr 25, 2024 · 5 comments
Open

Order of task execution #871

dikdom opened this issue Apr 25, 2024 · 5 comments

Comments

@dikdom
Copy link

dikdom commented Apr 25, 2024

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!

@kamikazechaser
Copy link
Collaborator

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.

@dikdom
Copy link
Author

dikdom commented 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?

@Joker666
Copy link

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

@sanudatta11
Copy link

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

@kamikazechaser
Copy link
Collaborator

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants