_AutomationActivityInstance

Per-activity execution within an automation run (1–31 days, UTC). Join JobID to _Job for send activities.

Schema last reviewed 2026-06-17

Open Interactive Workspace All data views

Opens _AutomationActivityInstance in the interactive canvas with SQL Sandbox.

Fields (15)

Field	Type	Flags	Relations	Description
`MemberID`	Number	—	—	Business Unit MID.
`JobID`	Number	FK, NULL	_Job.JobID _Sent.JobID	Email job ID when activity is a send.
`AutomationName`	Text(400)	—	—	Automation name.
`AutomationCustomerKey`	Text(400)	FK	_AutomationInstance.AutomationCustomerKey	Automation external key.
`AutomationInstanceID`	Text(36)	FK	_AutomationInstance.AutomationInstanceID	Parent automation run ID.
`ActivityCustomerKey`	Text(400)	—	—	Activity external key.
`ActivityInstanceID`	Text(36)	PK	—	Unique activity run ID.
`ActivityType`	Number	—	—	Activity type numeric ID (e.g. 300 = SQL Query).
`ActivityName`	Text(400)	—	—	Activity name.
`ActivityDescription`	Text(400)	NULL	—	Activity description.
`ActivityInstanceStep`	Text(25)	—	—	Step position (e.g. 3.2).
`ActivityInstanceStartTime_UTC`	Date	NULL	—	Activity start time (UTC).
`ActivityInstanceEndTime_UTC`	Date	NULL	—	Activity end time (UTC).
`ActivityInstanceStatus`	Text(256)	—	—	Activity run status.
`ActivityInstanceStatusDetails`	Text(4000)	NULL	—	Error details when status is Error.

Example query

SELECT TOP 100
  JobID, MemberID, AutomationName, AutomationCustomerKey, AutomationInstanceID, ActivityCustomerKey
FROM _AutomationActivityInstance

Valid in Query Studio and Automation Studio Query Activities. GROUP BY is only needed for aggregates; ORDER BY is optional but recommended with TOP so rows are meaningful. Narrow date ranges on large tracking views to avoid timeouts.