Rosa Gutierrez

Could you copy the full command you're using to run Solid Queue in each case?

What version are you running? What you describe sounds a lot like what was fixed in https://github.com/rails/solid_queue/pull/345 🤔 This would have been included in `1.0.0.beta`.

Ahhhh! So sorry about that! It should be fixed now 😅 About the issue with the configuration, yes, it's on my radar; I've got it in my plans to raise...

> Also reading the code I could see that `recurring.yml` supports nesting tasks under rails-env keys (production, staging, etc.) - knowing this would save me some time. Hmm... I think...

Oops, I forgot to close this one. Invalid configuration now raises an error thanks to https://github.com/rails/solid_queue/pull/427

Hey @vitobotta, no, not for Solid Queue, but there's [this one for Active Job](https://grafana.com/grafana/dashboards/17303-yabeda-activejob/).

Ahhhh, not really. You can check `finished_at` and compare it with `scheduled_at`, but that would include the time waiting in the queue. [Active Job instrumentation events](https://github.com/rails/rails/blob/5520bd835e3724ffafe3f719f9aafe951567f2f3/activejob/lib/active_job/instrumentation.rb#L26) are much better but...

No specific plans besides the instrumentation that already exists but I'm definitely open to ideas there!

@amirali-ashraf, could that perhaps live in https://github.com/rails/mission_control-jobs? Since that has controllers and specific code to query Active Job's queues and jobs 🤔

Hmmm... while for Solid Cache, you might want to simply fail open in that case, I'm not sure performing jobs inline is desirable in general. Have you found this behaviour...