# bunqueue v2.6.64

Fixes 1 bug. No-lock ack fails after stall re-queue (data loss): When a worker with useLocks=false processed a job that stall detection re-queued, the ack() call threw "Job not found" with no recovery path, leaving the job stuck in the…

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

---

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

Fixes 1 bug. No-lock ack fails after stall re-queue (data loss): When a worker with useLocks=false processed a job that stall detection re-queued, the ack() call threw "Job not found" with no recovery path, leaving the job stuck in the…

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

#### To install bunqueue v2.6.64

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

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

#### To upgrade bunqueue

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

## Bugfixes

- **No-lock ack fails after stall re-queue (data loss)**: When a worker with `useLocks=false` processed a job that stall detection re-queued, the `ack()` call threw "Job not found" with no recovery path, leaving the job stuck in the queue forever. The existing Issue #33 handler (`completeStallRetriedJob`) only fired when a lock token was present. Now the handler also fires for tokenless acks when the job was stall-retried (`attempts > 0`), preventing false completions of freshly-pushed jobs.

## Thanks to 1 contributor!

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

---

[← bunqueue v2.6.63](https://bunqueue.dev/blog/bunqueue-v2-6-63/) · [Release on GitHub](https://github.com/egeominotti/bunqueue/releases/tag/v2.6.64) · [Commits since v2.6.62](https://github.com/egeominotti/bunqueue/compare/v2.6.62...v2.6.64) · [Full changelog](https://bunqueue.dev/changelog/) · [All posts](https://bunqueue.dev/blog/)