Retrying failing jobs

Retrying failing jobs
When a processor throws an exception, the worker will catch it and move the job to the failed set. But sometimes, it may be desirable to retry a failed job.
BullMQ supports retries of failed jobs using backoff functions. It is possible to use the built in backoff functions or provide custom ones.
For BullMQ to reschedule failed jobs, make sure you create a QueueScheduler for your queue.
From BullMQ 2.0 and onwards, the QueueScheduler is not needed anymore.
The code below shows how to specify a "exponential" backoff function with a 1 second delay as seed value, so it will retry at most 3 times spaced after 1 second, 2 seconds and 4 seconds:
import { Queue } from 'bullmq';
​
const myQueue = new Queue('foo');
​
await queue.add(
  'test-retry',
  { foo: 'bar' },
  {
    attempts: 3,
    backoff: {
      type: 'exponential',
      delay: 1000,
    },
  },
);
You can also define it in the queue's defaultJobOptions, and it will apply to all jobs added to the queue, unless overridden. For example:
import { Queue } from 'bullmq';
​
const myQueue = new Queue('foo', {
  defaultJobOptions: {
    attempts: 3,
    backoff: {
      type: 'exponential',
      delay: 1000,
    },
  },
});
​
await queue.add('test-retry', { foo: 'bar' });
The current built-in backoff functions are "exponential" and "fixed".
With an exponential backoff, it will retry after 2 ^ attempts * delay milliseconds. For example, with a delay of 3000 milliseconds, for the 7th attempt, it will retry 2^7 * 3000 milliseconds = 6.4 minutes after the previous attempt. With a fixed backoff, it will retry after delay milliseconds, so with a delay of 3000 milliseconds, it will retry every attempt 3000 milliseconds after the previous attempt.
If you want to define your custom backoff you need to define it at the worker:
import { Worker } from 'bullmq';
​
const worker = new Worker('foo', async job => doSomeProcessing(), {
  settings: {
    backoffStrategy: (attemptsMade: number) => {
      return attemptsMade * 1000;
    },
  },
});
You can then use your "custom" strategy when adding jobs:
import { Queue } from 'bullmq';
​
const myQueue = new Queue('foo');
​
await queue.add(
  'test-retry',
  { foo: 'bar' },
  {
    attempts: 3,
    backoff: {
      type: 'custom',
    },
  },
);
Or if you want to define multiple custom backoff types you need to define like:
import { Worker } from 'bullmq';
​
const worker = new Worker('foo', async job => doSomeProcessing(), {
  settings: {
    backoffStrategy: (
      attemptsMade: number,
      type: string,
      err: Error,
      job: Job,
    ) => {
      switch (type) {
        case 'custom1': {
          return attemptsMade * 1000;
        }
        case 'custom2': {
          return attemptsMade * 2000;
        }
        default: {
          throw new Error('invalid type');
        }
      }
    },
  },
});
Stop retrying jobs
When a processor throws an exception that is considered as unrecoverable, you should use the UnrecoverableError class.
BullMQ supports moving jobs to failed when this error is thrown without retrying to process it.
import { Worker, UnrecoverableError } from 'bullmq';
​
const worker = new Worker('foo', async job => {doSomeProcessing();
throw new UnrecoverableError('Unrecoverable');
}, {
  connection
  },
});
​
await queue.add(
  'test-retry',
  { foo: 'bar' },
  {
    attempts: 3,
    backoff: 1000,
  },
);
Last modified 1mo ago