Cannot get job information #14
-
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Hi @arthurvanl! A couple of things here: Getting repeated job info via CLI Repeated jobs cycle through states: after processing, the next execution sits in # List all jobs in the queue, including delayed ones
bunqueue queue jobs <queue-name> --state delayed
# Or get a specific job by ID
bunqueue job get <job-id>If Job logs Yes, you can view job logs with: bunqueue job logs <job-id>The job must have called Tip: use Also — if you were having issues with repeated job data updates, please upgrade to v2.5.8 which fixes that (see #16). |
Beta Was this translation helpful? Give feedback.


Hi @arthurvanl!
A couple of things here:
Getting repeated job info via CLI
Repeated jobs cycle through states: after processing, the next execution sits in
delayedstate until its timer fires. To see it:If
bunqueue job get <id>returns nothing, the original job was likely already completed and removed (removeOnComplete: true). Each repeat execution creates a new job with a new ID — the original ID won't persist across repeats.Job logs
Yes, you can view job logs with:
The job must have called
job.log('mes…