You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When having a repeatable Job running and calling queue.removeRepeatable is just simply resolves a promise with null regardless of the removal of the job.
In the sample below I create a repeatable Job and watch on the queue for completed jobs matching the repeatable job id and try to remove the job.
When passing job.opts.repeat to removeRepeatable it removes the job as it should returning null, but just passing something wrong like {foo:"bar"} does nothing and also returns null.
Description
When having a repeatable Job running and calling
queue.removeRepeatable
is just simply resolves a promise withnull
regardless of the removal of the job.In the sample below I create a repeatable Job and watch on the queue for completed jobs matching the repeatable job id and try to remove the job.
When passing job.opts.repeat to
removeRepeatable
it removes the job as it should returningnull
, but just passing something wrong like{foo:"bar"}
does nothing and also returnsnull
.It would be greate when https://github.com/OptimalBits/bull/blob/master/lib/repeatable.js#L98
would return a meaningfull result from its
_this.client.RemoveRepeatable
call.Minimal, Working Test code to reproduce the issue.
test.js
hello_module.js
Bull version
^3.4.8
Additional information
The text was updated successfully, but these errors were encountered: