bun app quits before sandboxed processor is processed

[arthurvanl]

Problem

So it seems there is an easy fix but I just did not know how to:

const worker = new SandboxedWorker<EmailJob>('emails', {
  processor: './processor.ts',
  concurrency: 5,
  heartbeatInterval: 5000,
});
process.on('SIGINT', async () => {
    console.log('Shutting down...');

    while(true) {
        await sleep(1000);

        if(worker.getStats().busy === 0) { break; }

    }
    await worker.stop();
  shutdownManager();
  process.exit(0);
});

this fixes that running jobs are still processed fully

Proposed solution

Update the page: https://bunqueue.dev/guide/use-cases/#graceful-shutdown-pattern

Alternatives considered

No response

[arthurvanl]

Actually this is an issue I see, because docs show this:

[egeominotti]

Fixed in v2.6.9 (aab9a59).

Root cause: SandboxedWorker.stop() was immediately calling worker.terminate() on all worker threads, killing in-flight jobs without waiting for them to complete.

Fix: stop() now drains active jobs before terminating, matching the behavior of the regular Worker.close():

• Sets running = false to stop pulling new jobs
• Waits for all busy workers to finish their current jobs
• Keeps heartbeat alive during drain so locks don't expire
• Only terminates workers after all are idle

A force parameter was also added: await worker.stop(true) for immediate termination when needed.

So instead of the workaround polling getStats().busy, you can now simply do:

process.on('SIGINT', async () => {
  await worker.stop();  // waits for active jobs to finish
  process.exit(0);
});