sfmc // Automation HealthPRODUCTION

Automation Failures / Skips in the Last 24h

Surface recent unhealthy Automation Studio runs with the first error detail.

sqlautomation studioerrorskipped
Context Pack →Open Workspace →
Trust & provenancePRODUCTION
Evidence tierPRODUCTIONOfficial sources1Other sources0Last verified2026-10-05

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.

EvidencePRODUCTION
Difficultyfoundation
Verified2026-10-05
Use when

Daily operational health checks.

Investigating a downstream audience or Journey that suddenly stopped refreshing.

SELECT
    AutomationName,
    AutomationCustomerKey,
    AutomationInstanceID,
    AutomationInstanceStatus,
    AutomationInstanceStartTime_UTC,
    AutomationInstanceEndTime_UTC,
    AutomationInstanceActivityErrorDetails
FROM _AutomationInstance
WHERE AutomationInstanceEndTime_UTC >= DATEADD(day,-1,GETUTCDATE())
  AND AutomationInstanceStatus IN ('Error','Stopped','Skipped')
Why it works

The AutomationInstance status and UTC timestamps expose recent execution outcomes without relying on the UI history screen.

Operational notes

Skipped runs can indicate scheduling overlap or queued file-drop instances, not only manual intervention.

Related
Sources / verification