--- title: "Automation History" slug: "automation-history" updated: 2026-06-25T16:20:13Z published: 2026-06-25T16:20:13Z canonical: "documentation.lakesidesoftware.com/automation-history" --- > ## Documentation Index > Fetch the complete documentation index at: https://documentation.lakesidesoftware.com/llms.txt > Use this file to discover all available pages before exploring further. # Automation History The **Assist > Automation History** page shows all automation runs. It helps teams audit activity, troubleshoot failures, and understand how often automations run in the environment. ## Execution List The execution list table shows every automation run. Each row represents an execution and includes: - **Automation**: The name of the automation that ran. - **Time**: The date and time when the run started. - **Run By**: The user that ran the automation. - **Run From**: The value can include two parts: - Run source: - [Assist](/documentation/docs/assist-overview) - [Engagement](/documentation/docs/engagements) - Manual — run by an API call - [Prevent](/documentation/docs/prevent) - [Resolve](/documentation/docs/resolve) - [Self‑Help](/documentation/docs/self-help-app) — the Self Help app - [Sensor](/documentation/docs/sensor) — run automatically from a sensor - [ServiceNow](/documentation/docs/servicenow-integrations-assist-for-itsm) — Assist for ITSM - [SRE](/documentation/docs/systrack-reliability-engineering) — Reliability Engineering - [A2A, Direct API, or MCP](/documentation/docs/systrack-ai-setup) — a custom integration with SysTrack AI - [Microsoft Teams](/documentation/docs/systrack-ai-for-teams) — SysTrack AI for Teams - [Pulse](/documentation/docs/systrack-pulse-guide) — the SysTrack Pulse browser extension - [Voice](/documentation/docs/systrack-ai-voice) — SysTrack AI Voice - **Unknown** — The agent version does not recognize the run source. This can occur when automation history includes a trigger type that was added after the agent was released. Update the agent to show the specific run source. - Run trigger detail: - **AI** — auto diagnostics suggested the automation - **Remediation** — the automation was linked to a detected issue - **Tools** — a user manually selected the automation - For **Engagement** runs — the name of the engagement that ran the automation - For **Sensor** runs — sensor names are shown separately in the **Related Sensors** column - **Related Sensors**: Any sensors linked to the automation. - **Error**: The error details when the run fails. This field is empty for successful runs. ![](https://cdn.document360.io/87d11426-6b1f-4b19-b593-b71e55a81af3/Images/Documentation/image(134).png) ## Execution Frequency Chart The execution frequency chart shows how often automations were run over time. - Each bar shows the number of runs on a specific date. - Successful and failed runs are shown within the same bar using different colors. ![](https://cdn.document360.io/87d11426-6b1f-4b19-b593-b71e55a81af3/Images/Documentation/image(135).png)