# bunqueue v2.8.11

Fixes 6 bugs. FAIL now carries the stack (stack: string[], optional, old clients unaffected).

Canonical: https://bunqueue.dev/blog/bunqueue-v2-8-11/

---

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

Fixes 6 bugs. FAIL now carries the stack (stack: string[], optional, old clients unaffected).

![](https://github.com/egeominotti.png?size=64) [egeominotti](https://github.com/egeominotti)

#### To install bunqueue v2.8.11

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

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

#### To upgrade bunqueue

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

## Bugfixes

The 2.6.110 fix populated `job.stacktrace` only on the worker's in-process
`failed` event object. The stack never reached the server: `FAIL` carried just
the error message, so `queue.getJob(id).stacktrace` was always `null` (the
TCP job proxy even hardcoded it), DLQ entries had no stack, and any process
other than the failing worker could never see it. Reported again on #74
("I need the stacktrace").

- **`FAIL` now carries the stack** (`stack: string[]`, optional, old clients
  unaffected). The worker sends the failure's stack lines alongside the error
  message in both TCP and embedded mode.
- **Persisted on the job**: the last failure's stack is stored on the domain
  job (trimmed lines, capped at `stackTraceLimit`, default 10), survives
  retries and server restarts (new `jobs.stacktrace` column, migration 13),
  and rides into the DLQ entry when attempts are exhausted.
- **Readable everywhere**: `queue.getJob()` / `getJobs()` now return the real
  `stacktrace` (TCP + embedded, the proxy no longer hardcodes `null`), DLQ
  entries expose it via `entry.job.stacktrace`, and fetched jobs also reflect
  `failedReason` (derived from the persisted timeline).
- HTTP `POST /jobs/:id/fail` accepts the same optional `stack` array.
- Defensive caps along the wire: client sends at most 50 lines, server accepts
  at most 100, the job's own `stackTraceLimit` is authoritative.
- The worker `failed` event behavior is unchanged (and now covered by
  regression tests replicating the exact reporter scenario: TCP + auth +
  cron scheduler + preventOverlap/skipIfNoWorker).

## Thanks to 1 contributor!

- [@egeominotti](https://github.com/egeominotti)

---

[← bunqueue v2.8.10](https://bunqueue.dev/blog/bunqueue-v2-8-10/) · [Release on GitHub](https://github.com/egeominotti/bunqueue/releases/tag/v2.8.11) · [Commits since v2.8.10](https://github.com/egeominotti/bunqueue/compare/v2.8.10...v2.8.11) · [Full changelog](https://bunqueue.dev/changelog/) · [All posts](https://bunqueue.dev/blog/)