Skipped Automations Are Often a Scheduling Smell
An automation has Skipped instances even though nobody intentionally skipped it.
Trust & provenancePRODUCTION
Evidence tierPRODUCTIONOfficial sources1Other sources0Last verifiedNot recorded
Evidence tier describes my hands-on relationship with the content. Official sources describe platform contracts/documentation. Production observations should not automatically be treated as official limits.
Salesforce notes skipped instances can indicate unhealthy scheduling, including insufficient time between scheduled runs or queued file-drop instances.
What to check
- Compare average/max runtime with schedule interval.
- Inspect _AutomationInstance for Skipped status.
- Look for upstream file drops/queued instances around the same time.
Make it cheaper next time
- Leave runtime headroom between recurring runs.
- Track duration trends instead of monitoring only Error status.
automation studioskippedschedulehealth