Replies: 2 comments 1 reply
-
Is that exact code running on the latest version of BullMQ producing that error? I am wondering because we have a test cases that cover exact this case: https://github.com/taskforcesh/bullmq/blob/master/tests/test_worker.ts#L2306 |
Beta Was this translation helpful? Give feedback.
1 reply
-
Closing this in favor of the issue #1896 where I managed to reproduce the issue |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
When the error is caught, it does get delayed, but throws the following error:
1683996065811 - Worker is processing an embeddings creator job...
422 error, removing job
Error: Missing lock for job 1431. failed
at Scripts.finishedErrors (/Users/alessio/Documents/GitHub/payload-plugin-ai-impl/node_modules/bullmq/src/classes/scripts.ts:332:16)
at Job.moveToFailed (/Users/alessio/Documents/GitHub/payload-plugin-ai-impl/node_modules/bullmq/src/classes/job.ts:648:26)
at processTicksAndRejections (node:internal/process/task_queues:95:5)
at async handleFailed (/Users/alessio/Documents/GitHub/payload-plugin-ai-impl/node_modules/bullmq/src/classes/worker.ts:658:11)
at async Worker.retryIfFailed (/Users/alessio/Documents/GitHub/payload-plugin-ai-impl/node_modules/bullmq/src/classes/worker.ts:874:16)
Why is that? I'm passing the token in the moveToFailed function, so why am I getting a "Missing lock" error?
Beta Was this translation helpful? Give feedback.
All reactions