why do I get invalid or expired lock token?

[arthurvanl]

still using embedded btw

My SandboxedWorker:

export const productWorker = new SandboxedWorker(ModuleName.Product, {   
    processor: 'src/modules/product/index1.sync.ts',
    concurrency: 3, //parralel 3 syncs that can run
    maxMemory: 512, //512MB
    timeout: 1000 * 60 * 60 * 24 // allowed to be ran 24 hours
})
//* no 'active' listener here as we add the sync into db when adding chained jobs
.on('error', (error) => console.log('product worker error:', error))
.on('failed', (job) => endListener()(job as Job<UniversalJobData>))
.on('completed', (job) => endListener()(job as Job<UniversalJobData>)) 

[arthurvanl]

I am not sure if this is the case but I did not use a graceful shutdown yet. So maybe old jobs that werent removed properly were maybe still in cache??? I removed the cache from the /tmp folder that I saw. I dont get the errors anymore now.

[egeominotti]

Fixed in v2.6.4. The root cause was a race condition between the background lock expiration task and fail(). When the lock expired, the background task cleaned it up and requeued the job — then fail() would throw because the token was gone. Now fail() gracefully handles this case and returns silently when the job was already requeued.

[arthurvanl]

One more addition to this: I was node:cluster. So I ended up with 5 workers instead of one and 5 queues instead of one. Does this matter in the end?

[arthurvanl]

Im still receiving the same error: