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
Greetings,
For some reason, we've been encountering an issue of disappearing/stuck batch jobs.
Those jobs do not finish. does not enqueue and cannot be found in either Queue, Busy or Retryset.
they are stuck in a pending state in the batch until for some unknown reason they get "start" working again.
this time is random. sometimes at 3 am sometimes at 1 pm.
Does anyone else encounter this issue? was it resolved in the more recent sidekiq versions?
Thanks in advance,
Daniel
The text was updated successfully, but these errors were encountered:
One more question.
What are the possible reason for the batch, on success not to be called?
Currently, I've got a batch with all of his jobs finished successfully.
and the batch's on_success callback is not being received. even though the queue is empty.
Ruby version:
2.5.5
Rails version:
5.1.6
Sidekiq / Pro / Enterprise version(s):
sidekiq-pro (5.0.0)
Greetings,
For some reason, we've been encountering an issue of disappearing/stuck batch jobs.
Those jobs do not finish. does not enqueue and cannot be found in either Queue, Busy or Retryset.
they are stuck in a pending state in the batch until for some unknown reason they get "start" working again.
this time is random. sometimes at 3 am sometimes at 1 pm.
Does anyone else encounter this issue? was it resolved in the more recent sidekiq versions?
Thanks in advance,
Daniel
The text was updated successfully, but these errors were encountered: