blog · release

bunqueue v2.7.15

Fixes 1 bug. Cron/scheduler jobs ignored job options (#86): Jobs spawned by upsertJobScheduler/cron always used JOB_DEFAULTS (maxAttempts: 3, removeOnFail: false), ignoring both the scheduler job template opts and the Queue…

egeominotti

To install bunqueue v2.7.15

bun add bunqueue@2.7.15

npm install bunqueue@2.7.15

To upgrade bunqueue

bun add bunqueue@latest

Bugfixes

• Cron/scheduler jobs ignored job options (#86): Jobs spawned by upsertJobScheduler/cron always used JOB_DEFAULTS (maxAttempts: 3, removeOnFail: false), ignoring both the scheduler job template opts and the Queue defaultJobOptions. A scheduler with attempts: 1, removeOnFail: true still retried 3× and landed failed jobs in the DLQ. Cron definitions now carry a jobOptions field (maxAttempts, backoff, timeout, delay, stallTimeout, removeOnComplete, removeOnFail) that fireCronJob forwards into each spawned job. The client merges Queue defaultJobOptions (base) with per-scheduler template opts (override), mapping attempts → maxAttempts. Persisted via new job_options column (schema migration 12); old rows load as null and fall back to defaults.

Notes

• For cron jobs, removeOnComplete/removeOnFail honor only the boolean form. The numeric/KeepJobs variants accepted by queue.add() are not applied to scheduler-spawned jobs and fall back to false.
• A per-job delay set in scheduler options stacks on top of the cron fire time (the spawned job is delayed delay ms after each scheduled fire).

Thanks to 1 contributor!

• @egeominotti

---

← bunqueue v2.7.14 · Release on GitHub · Commits since v2.7.14 · Full changelog · All posts