Skip to content
Discussion options

You must be logged in to vote

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 delayed state until its timer fires. To see it:

# 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 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:

bunqueue job logs <job-id>

The job must have called job.log('mes…

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@arthurvanl
Comment options

Answer selected by arthurvanl
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants