Hey
@Lee Mendelowitz, thought about this a bit. I do think we’ll be able to address this in a cleaner way in the coming month or two with more highly customizable work queue health policies. that said, I think for now posting a custom trigger via API might help. The docs are
here, you could up the threshold and within keys to only fire the trigger if it saw two wq unhealthy events in 10 minutes, for example. So that first wq unhealthy event (fired when the run was deemed late for taking 90 seconds to spin up) wouldnt trigger the alarm, but if two happened, it would.