NestJS Bull queues - Missing lock for job failed

Question

I'm using Bull with NestJS to handle a jobs queue. In the process handler I would like to mark a job as failed instead of completed, but it seems - also reading the documentation - that the Job#moveToFailed() method is allowed only on waiting jobs.

In fact, it triggers an error saying "Missing lock for job ${jobId} failed". But, calling the Job#moveToFailed with the ignoreLock parameter to true everything goes fine.

What happens if I ignore the lock moving a job to failed? Is there some side effect? In my scenario, the queue jobs will be always consumed by the same @Processor.

Here it is the piece of code I'm running for test purpose:

@Process()
async transcode(job: Job<unknown>): Promise<any> {
  const jobData = job.data as Record<string, string | unknown>
  if (jobData == null) {
    await job.moveToFailed({ message: 'Hook marked as failed because of missing data' })
    return
  }

  // do other stuff for job execution..
}

set `ignoreLock` [DOC](https://github.com/OptimalBits/bull/blob/master/REFERENCE.md#jobmovetofailed) — Empty Brain, Jun 04 '22 at 21:03
as I wrote @EmptyBrain, is there some side effect telling bull to ignore the lock? — andrea.rinaldi, Jun 06 '22 at 14:13

jakobinn · Accepted Answer · 2023-02-23T14:35:16.777

1

You can pass false as a token parameter (that ignores the token check).

await job.moveToFailed({ message: 'Hook marked as failed because of missing data' }, false)

I was able to add '0' instead of false and that worked for me, but the parameter type is Boolean like mentioned in the comments below.

edited Feb 23 '23 at 14:35

answered Aug 06 '22 at 15:52

jakobinn

1,832
1
20
20

Yes, I forgot to edit. We arrived at the same conclusion, it seems the only way to make it work properly. – andrea.rinaldi Sep 09 '22 at 13:00
1

Its throwing error like `Argument of type 'number' is not assignable to parameter of type 'boolean'.` – Ritesh Khatri Dec 29 '22 at 08:20
Use false in place of "0". The type looks like this: (method) Bull.Job.moveToFailed(errorInfo: { message: string; }, ignoreLock?: boolean): Promise<[any, Bull.JobId]> – Abulo John Joshua Feb 13 '23 at 11:18
@RiteshKhatri you can pass `undefined` for the token param – rolling_codes Mar 01 '23 at 19:42

NestJS Bull queues - Missing lock for job failed

1 Answers1