# bunqueue v2.6.84

Fixes 1 bug. immediately: true conflicting with skipMissedOnRestart (#65): - immediately now only fires on first creation, not on subsequent upserts - Previously, every call to upsertJobScheduler with immediately: true would override…

Canonical: https://bunqueue.dev/blog/bunqueue-v2-6-84/

---

<!-- Generated from changelog.md by docs/scripts/generate-release-posts.ts. Edit the changelog and regenerate. -->

Fixes 1 bug. immediately: true conflicting with skipMissedOnRestart (#65): - immediately now only fires on first creation, not on subsequent upserts - Previously, every call to upsertJobScheduler with immediately: true would override…

#### To install bunqueue v2.6.84

```bash title="bun"
bun add bunqueue@2.6.84
```

```bash title="npm"
npm install bunqueue@2.6.84
```

#### To upgrade bunqueue

```bash
bun add bunqueue@latest
```

## Bugfixes

- **`immediately: true` conflicting with `skipMissedOnRestart`** ([#65](https://github.com/egeominotti/bunqueue/issues/65)):
  - `immediately` now only fires on **first creation**, not on subsequent upserts
  - Previously, every call to `upsertJobScheduler` with `immediately: true` would override `skipMissedOnRestart` and fire the cron immediately, even after a server restart
  - This was the root cause of the TCP-mode report: the user's app called `upsertJobScheduler` on every startup with both flags, causing the cron to fire immediately despite `skipMissedOnRestart`

---

[← bunqueue v2.6.83](https://bunqueue.dev/blog/bunqueue-v2-6-83/) · [Full changelog](https://bunqueue.dev/changelog/) · [All posts](https://bunqueue.dev/blog/)