Rosa Gutierrez

> This would start the metrics server within the supervisor and exposes the metrics. From the perspective of SolidQueue, that should be sufficient, right? Yes, that should be it 🤔...

Hey @Envek so sorry for not replying before! I somehow missed this notification completely 😳 What you have is correct, and I agree about measuring latency. The grouping itself should...

Sorry for the delay here, @MrSerth! I'll look into this one very soon.

Hey @MrSerth, in the end, after some back-and-forth, we're going to remove the Puma plugin completely https://github.com/rails/solid_queue/pull/303, so I think you could perhaps run Solid Queue separately. I plan to...

In the end, [we're going to keep the Puma plugin](https://github.com/rails/solid_queue/pull/303#issuecomment-2332549561), so I'm going to reopen this one! 😅

Hey @Ed1lan, sorry about that! Those jobs should be released automatically (marked as failed) when the supervisor starts next time. Is this happening in development only? Was your computer going...

> Maybe the backup shutted down the workers? But after that they didn't got marked as failed as they supposed to Hmm no, that shouldn't be related 🤔 They could...

> No, it didn't. Those jobs stayed in-progress and claimed as shown in the others screenshots. And they didn't get released when you restarted the supervisor? Releasing in-progress jobs happens...

Going to close this one.

> when I pass an invalid path via `SOLID_QUEUE_RECURRING_SCHEDULE` then SolidQueue defaults to the default `config/recurring.yml` configuration file Hmm... I'm not seeing this. When I pass an invalid path via...