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

jobs are not run consecutively #90

Closed
JanMP opened this issue Apr 15, 2020 · 2 comments
Closed

jobs are not run consecutively #90

JanMP opened this issue Apr 15, 2020 · 2 comments

Comments

@JanMP
Copy link

JanMP commented Apr 15, 2020

I need jobs to make sure that some lengthy async functions (awaiting results before calling this.success) are run consecutively in the order Jobs.run was called. But I can't get it to work. I make no use of any timing features and all priorities are at default.

I start a lengthy job, the status is shown as pending. 10ish seconds later I start a quick job (while job 1 is still pending) and it is quickly going to pending and then success. Then a couple minutes later job 1 is finally done and switching to success.

@JanMP
Copy link
Author

JanMP commented Apr 15, 2020

ah ok, i think i get it. When I register a job it creates it's own que. Is there an elegant way to have different kinds of jobs que up in the same line (besides creating a job that then runs a switch statement to run different functions)?

@msavin
Copy link
Owner

msavin commented Apr 19, 2020

Hey - thanks for using Steve Jobs!

Up until the new 4.0 (just published), the package did not support async functions, which is why the jobs ran all at once. It should be good to go now, please let me know if you run into any issues!

@msavin msavin closed this as completed Apr 19, 2020
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

2 participants