I was working with a customer recently and we realized that when using the “Schedule” functionality the most granular re-occurrence interval available is 1 hour. In this particular case, we needed to check service status every 5 minutes and send the data to OMS to alert and trigger a remediation runbook, so 1 hour would not suffice. I had recently spoken with a member of the product group around a custom OMS solution and specifically remembered him saying that his runbook was running every 5 minutes….so I was off to investigate!
After a few minutes of searching, I was able to find some good information here. Although the post referenced the Classic portal, the same basic process still applies and worked in my scenario. By using a Scheduler Collection we can schedule at a much more granular interval. I’ve outlined the process in the new portal below.