Felix Mosheev

Hi @jyotirmoy-bst, looks like you are using a really old version of `bull-board`, can you update to latest and check if it solves your problem?

@whydnxx can we close this issue?

Sounds like reasonable PR is always welcome

There is no `stuck` status of a job in bullmq. There is a term called [`stalled`](https://docs.bullmq.io/guide/jobs/stalled) which refers to a job that it's queue didn't got any updates regarding it....

@fogine thank u for the info. From the test case that you've posted, looks like a job become stuck when ```js await job.releaseLock(); await job.remove(); ``` Do u really have...

I've tried to add the `stuck` status, but it is not supported by bullmq & bull types, https://github.com/taskforcesh/bullmq/blob/master/src/types/job-type.ts#L10 I don't think that it is smart to add internal statuses.

Same issue applies to `bull`, [source code](https://github.com/DefinitelyTyped/DefinitelyTyped/blob/master/types/bull/index.d.ts#L321)

ioredis_mock can't work in the browser since it requires some lua stuff.

I'm not sure regarding that, but sounds like bull should handle this... This lib calls bulls queue.clean, if it doesn't remove all the parts it is bull's bug. Wdyt?

Ping?