When search concurrency limits or high SVC saturation hit a Search Head, Splunk skips scheduled alerts and reports, logging each skipped run to index=_internal under sourcetype=scheduler with status=skipped.
Investigating skipped searches directly in _internal complements the Cloud Monitoring Console by revealing the exact savedsearch_name and skip reason (such as reaching maximum concurrent search limits).
Write an SPL query against index=_internal sourcetype=scheduler status=skipped to count skipped runs by savedsearch_name and reason.
index=_internal sourcetype=scheduler status=skipped
| stats count by savedsearch_name, reason
| sort -count