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
Sometimes when trying to obliterate queue, we get the error: Error: Cannot obliterate non-paused queue
I've noticed this often when trying to obliterate again the same queue after re-creating in the Redis.
Sometimes we're getting the error the first time using it.
One more thing is the key with stalled-check getting created into Redis and we don't have idea what this is coming from.
The text was updated successfully, but these errors were encountered:
@aislanmaia In order to guarantee that no running jobs are kept hanging after an obliteration, by default the queue is paused but will fail if there are active jobs on it. However (although not recommended) you can force away from this behaviour: https://github.com/OptimalBits/bull/blob/develop/REFERENCE.md#queueobliterate
But I thinking that the error message itself is wrong here, it should probably say "Cannot obliterate queue with active jobs in it"
Sometimes when trying to obliterate queue, we get the error:
Error: Cannot obliterate non-paused queue
I've noticed this often when trying to obliterate again the same queue after re-creating in the Redis.
Sometimes we're getting the error the first time using it.
One more thing is the key with
stalled-check
getting created into Redis and we don't have idea what this is coming from.The text was updated successfully, but these errors were encountered: