How to investigate Oban jobs stuck in 'available' state, across all queues?

@sorentwo We also faced exact issue sometime ago, and we too had to restart the server for jobs to move into executing state. But we have only single node. Any idea on how can we monitor/debug issue like this.

We can see in this image that these jobs were in available state for 4hrs…

Also once we restarted there was big cpu spike (as expected) due to all these pending jobs moving to exectuing state at once.