Manuel Astudillo
Manuel Astudillo
@Haris-SP4RKy you should check the keys that include the "id" as postfix, as those are the actual jobs
The would look something like this: ``` "bull:test-39244dbe-5287-4d5b-9815-964ee48acc53:id" ```
You can also check the contents of the events key, as for example this one ```"bull:test-0dc5b09d-2727-4595-8e43-37e7dc366bcb:events"```
@magnusburton stalled or not, jobs take always the same amount of memory. When jobs are in different statuses, we only store the job id, which by default is a increasing...
I am not sure that I understand what you mean. If you add 2 delayed jobs one after each other they will be processed directly, put on the delay set...
In other words, a delayed job does not delay the whole queue, it only delays that job in particular...
Unfortunately this is working as design. In the previous versions of BullMQ, we did not store a meta object for every job scheduler, instead the scheduler was encoded in the...
@webfrank you do not need to use the redis prefix just pick a different prefix in BullMQ (default is "bull")
@loris I cannot say if the errors are due to older version of the cron jobs but I do not think so, but it is quite suspicious that it happens...
@webfrank the problem is that the prefix needs to be applied internally in lua scripts too. So design wise it is better to let BullMQ handle all the prefixing, otherwise...