Azure Automation Hybrid Workers stuck in Queue

Okay, please someone explain something to me.

I have been working with PowerShell runbooks for over 5 years now and running into this issue has always eluded me. The only real way to monitor how PS runbooks work on a Hybrid worker is to stumble on the right one's Event Viewer. You will notice a few cryptic events happening about a 'sandbox' here and a 'hybrid runbook' there, referencing the runbook being ran.

What I don't understand is why i notice it 'pings' a slew of events continuously while the UI shows its in 'Queue'. There is no indication if it will even pick it up and most of the time the errors thrown are horrible to identify. It rarely shares cmdlet errors if the service fails. So what am I missing? Can someone give me an explanation that doesn't involve the inadequete documentation MSoft provides. I can of course get logs of bad cmdlets using Azure Analytics, but it doesn't explain the service. I also know it 'pings' the service every 30 seconds to get some jobs, but why does it SHOW its found the job, but won't actually take the job. It even says it drops it...

Someone please help me with this insanity!