Queue#upsertScheduler starts right away....

[arthurvanl]

I am using vesion 2.6.95 (both in tcp and client)

Originally posted by @arthurvanl in #72

I still not working like at all:

• now it always starts right away????
• and other issue is still not fixed (when job running longer than pattern & app stopped, after restart job right away)

@egeominotti this is going on since the first time I started using this.

[arthurvanl]

It also doesn't open the workers....

It also didnt add all workers:

My setup:

Im starting to dislike the tool because of this. Please fix this

[egeominotti]

This is an open source project. If you'd like to help with development, nothing is taken for granted, as it's free. I hope you understand.

You're asking for features that weren't on bunqueue, it's a complex project if something doesn't work and you don't like it, do as you wish.

If you want to help you have to paste all the code no screenshots, from now on I will close every issue you open with images.

[arthurvanl]

This is an open source project. If you'd like to help with development, nothing is taken for granted, as it's free. I hope you understand.

I understand that. But it's kinda annoying if you get told that something is fixed and after testing each time it has not been changed. Just a big frustration for me.

[arthurvanl]

If you want to help you have to paste all the code no screenshots, from now on I will close every issue you open with images.

That seems fair. I understand

[egeominotti]

If you want to help the project, please paste the actual code examples because you are leading me astray with your incomplete and partial examples.

[arthurvanl]

I thought the screenshots were enough proof. But next time ill try to make a reproduction.

[egeominotti]

If you reproduce the problem for me with real code, we can solve it very easily so it is really impossible to understand well.

[arthurvanl]

Okay ill do that in a sec!

[egeominotti]

@arthurvanl I thank you for the bugs you find, but you must help me reproduce them faithfully otherwise I cannot fully understand every detail. This step is essential.

[egeominotti]

Fixed in the next release (cron scheduling part).

Root cause: skipMissedOnRestart defaulted to false, so when the server restarted, load() kept past nextRun values as-is. The scheduler then saw nextRun < now and fired the cron immediately.

Fix: Changed the default of skipMissedOnRestart to true. On restart, past-due crons now recalculate nextRun to the next future occurrence instead of firing immediately. If you explicitly need catch-up behavior, you can opt in with skipMissedOnRestart: false.

This also fixes the case where a job runs longer than the cron interval and the app restarts — the missed execution is skipped and the cron resumes on its normal schedule.

---

Regarding the workers closing immediately and not all workers appearing in bunqueue worker list — I can't diagnose this from screenshots alone. Could you please paste the actual code that creates and starts the workers? Specifically:

1. How you create the Queue and Worker instances
2. Where they are stored (are they in a top-level variable or inside a function?)
3. The full startup sequence

A minimal reproduction script would be ideal. Thanks for your patience.

[arthurvanl]

Okay I got a reproduction now @egeominotti