Rosa Gutierrez

Hey @Benoit-Baumann, thanks for your kind words! Ahhh, `whenever` is super cool! That's a great feature. If I understand this correctly, the logger that you'd want to override would be...

Hey @darinwilson, sorry for the delay and radio-silence on this one. I continued thinking about this, and I'm not convinced this is the right way to handle the problem. I...

Hey @lrjbrual, sorry for the delay! It's odd that the job stops being scheduled. When this happens, can you check which processes are running in the server where you're running...

Huh, what did it happen between this ``` 0 1000 59 42 20 0 836564 228588 ? Sl ? 0:05 solid-queue-supervisor(1.1.0): supervising 71, 74, 78 0 1000 71 59 20...

Hey @lrjbrual, so sorry for the delay replying! Somehow I missed the notification for your last comment 🤦‍♀️ You don't need to manually clean up any DB connection, Solid Queue...

> This proposal changes case (2) to not re-raise the exception if the job is not retried. The error is still logged by ActiveJob, but the error is not propagated...

> Therefore, I don't believe that "retried jobs are not treated as newly enqueued jobs" can be handled with the current return value / exception handling of `ActiveJob::Base.execute`. Maybe that's...

> Sidenote: In the practice of operating a queue, I think many folks try to differentiate between "We have intentionally decided to accept these known job exceptions and not retry...

Hey @InteNs, thanks for the detailed report. I'll look into this!

@InteNs, would you happen to have some more logs right before the restart? That is, a few more lines before this: ``` gate_worker.1.bxrxeomly8pa8gvvvdxot19pe@staging-docker-worker-3 | 2024-07-24 12:48:42.267770 I [T5600] SolidQueue --...