Jobs Queue system instable and lacks proper documentation

[yonnic]

hey guys, for 3 days i am trying to get this Jobs Queue system to work but the instability and lack of documentation is a huge blocker for me - thinking about to ditch it completely.

Here is whats wrong about it.

• It is not clear where to put "waitUntil" It was mentioned once in the docs but its not clear how to use it.
• Calling /api/payload-jobs/run never works for me, i always get "No jobs to run".
• Running npx payload jobs:run --queue default randomly works sometimes but get stuck after a response, or it process for 20 sec and returns nothing.
• deleteJobOnComplete: false, seems to have no effect, once a job was run its gone - how to do cron then ?

There are so many other things missing in the docs or as features.

• How to list jobs ?
• How to delete jobs ?
• How to monitor or check "processing" jobs (saw it in the response on job creation)

I really like the concept of this system and how its suppose to work, but at current state it has too many flaws and is unusable sadly. Maybe something is messed up on my instance but everything else works perfectly fine.

Payload 3.0.2
Node v20.15.1
Mac OS Sequoia 15.2

[yonnic]

seems like no one actually tried or use the Jobs system, will check if i create an issue here for every bug i had with it

[DanRibbens]

We just merged #9283 that will properly delete completed jobs.

[DanRibbens]

Calling /api/payload-jobs/run never works for me, i always get "No jobs to run".

This was addressed #9509 released v3.1.1

Running npx payload jobs:run --queue default randomly works sometimes but get stuck after a response, or it process for 20 sec and returns nothing.

This might have been because of an issue we found and patched in v3.0.1.

We will continue to improve the jobs queue and the docs and appreciate your feedback!

[MinskLeo]

Hi! Would be cool to actually see the example of scheduling using waitUntil. I agree - thats very unclear where the property should be set.