Is there an ignoreLock option for moveToCompleted?

[Pro-Ton]

Hi, In the Bull3 I had a manual handling queue in which clients sent completed jobs to a REST endpoint and I could move them to completed like this:

const id = req.params.id;
const returnValue = req.body;
const job = await tasksQ.getJob(id);
await job?.moveToCompleted(returnValue , true, true);

But in the BullMQ I wasn't able to produce such functionality:

I tried:

const job = await tasksQ.getJob(id);   // Also: await Job.fromId(tasksQ, id);
await job.moveToCompleted(returnValue, 'my-token', false);

But I get exception:
Error: Missing lock for job 14.

Clearly there was an option to ignoreLock in the previous version. I searched the docs but couldn't find similar option. Is there any options or other way of doing such functionality?

Thanks for the amazing work.

[manast]

https://docs.bullmq.io/patterns/manually-fetching-jobs

[Pro-Ton]

Thanks for your comment, I've read that page. But my use case is different.

When I use getNextJob I'm able to moveToCompleted the returned job.
But the problem is that I'm not able to use getNextJob because the external worker is outside the scope of my node application.
It provides the job ID, so I should get the job by it's ID, moveToCompleted the job, and save it's returnvalue.

[manast]

Then use the same token id for everything and it should work.

[Niek]

@Pro-Ton did you find a solution for this? I have the exact same use-case (manually processing jobs, given a specific ID), and the following code doesn't work:

const job = await queue.getJob(id)
job && job.moveToCompleted('returndata', 'token', false)

It throws with the error Error: Missing lock for job <ID>. finished

[StringKe]

@Niek Did you solve this problem?

[Niek]

@StringKe not really - see #1152 for a more extensive discussion.