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
Workers started with QUEUE=* do not cause error when there are no queues
* This should rarely happen (if at all) in production, but in
development, we ran into annoying situations if Redis were cleared and
we tried to start a catch-all Resque worker (via Foreman).
* The worker that is started will not process jobs, but at least it will
not die immediately with a bad exit code (which would stop all
processes in Foreman, for instance).
0 commit comments