---
title: "Tools in Resolve"
slug: "actions-tools"
updated: 2026-06-25T16:20:13Z
published: 2026-06-25T16:20:13Z
canonical: "documentation.lakesidesoftware.com/actions-tools"
---

> ## 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.

# Tools in Resolve

To run and manage automation‑related activities in Resolve, go to **Resolve** > **Tools**. The following tabs are available:

- Administrator Actions
- Run [Automations](/documentation/docs/automations-4)
- Run [Collection Extensions](/documentation/docs/collection-extensions-2)
- Run [Engagements](/documentation/docs/engagements)
- Automation History
- Collection Extension History

## Administrator Actions

This tab displays the available actions that can be run on endpoint systems. The **Reboot** action is automatically available on this tab. Users with appropriate rights can use the **Reboot** action to reboot the focus system (the endpoint system that you are currently viewing in SysTrack Resolve).

## Run Automations

### 

To run an automation, follow these steps:

1. Go to **Resolve**.
2. [Select the system](/documentation/docs/change-focus-in-resolve) on which you want to run the automation.
3. Select **Tools** from the menu on the left-hand side of the screen.
4. Select the **Run Automations** tab.
5. From the **Run Automations** tab, browse through the list of automations and select one. Automations are grouped by category, with unassigned ones listed under **Uncategorized**. Selecting an automation displays its description in the right panel.

> [!NOTE]
> **NOTE**: In Resolve, the **Run Automations** tab only displays automations that are applicable to the operating system of the focus system. To view or run automations for other operating systems, switch to a system running that OS.

1. If applicable, enter any parameter values in the **Parameters** section (on the right).
2. Under **Execution**, make a selection in the **Run Mode** field. The Run Modes do the following:

- **Run Silently**: The sensor is triggered on the agent. The automation runs in the background with no user input. It will not affect the user experience.
- **Prompt**: The sensor may interrupt the user workflow so the system opens a dialog box that prompts the user to respond yes or no if the automation will run.
- **Notify**: The sensor runs and the system opens a dialog box letting the user know that the automation will run. The user has no option to stop the automation.

For automations with **Notify** or **Prompt**, notifications are sent to the Self-Help app, which requires a Windows operating system.

1. Click the **Run** button

## Run Collection Extensions

To run a collection extension, follow these steps:

1. Go to **Resolve**.
2. [Select the system](/documentation/docs/change-focus-in-resolve) on which you want to run the automation.
3. Select **Tools** from the menu on the left-hand side of the screen
4. Select the **Run Collection Extensions** tab.
5. From the **Run Collection Extensions** tab, browse through the list of collection extensions and select one. Selecting a collection extension displays its description in the right panel. To receive collection extensions, systems must have Windows as an operating system and be connected to SysTrack.
6. If applicable, enter any parameter values in the **Parameters** section.
7. Click the **Run** button on the right-hand side of the screen to run the collection extension.

## Run Engagements

To run an engagement, follow these steps:

1. Go to **Resolve**.
2. [Select the system](/documentation/docs/change-focus-in-resolve) on which you want to run the automation.
3. Select **Tools** from the menu on the left-hand side of the screen
4. Select the **Run Engagements** tab.
5. From the **Run Engagements** tab, browse through the list of engagements and select one. Selecting an engagement displays its description in the right panel. To receive an engagement, systems must have Windows as an operating system and be connected to SysTrack. Engagements are sent to systems using the Self-Help app.
6. If applicable, enter any parameter values in the **Parameters** section.
7. Click the **Run** button on the right-hand side of the screen to run the engagement.

## Automation History

The **Resolve** > **Automation History** page shows all automation runs. It helps teams audit activity, troubleshoot failures, and understand how often automations run in the environment.

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.
- **User Interaction**: Indicates whether the automation required user interaction during execution.
  - **Silent** — the automation ran without prompting the user.
  - **Not Supported** — user interaction is not supported for this automation.
  - **Pending** — user approval is pending, and the system is awaiting a response.
  - **User Approved** — the user approved the automation to proceed.
  - **User Declined** — the user declined the automation.
  - **User Not Prompted** — the user was not prompted, for example, because conditions were not met.
  - **Notify** — the user was notified about the automation execution.
- **Run as User**: The user account under which the automation was executed.
- **Error**: The error details when the run fails. This field is empty for successful runs.
- **Return Code**: The numeric result returned by the automation after execution. A return code of **0** typically indicates a successful run, while non‑zero values indicate an error or abnormal termination.
- **Runtime (sec)**: The total time, in seconds, that the automation took to complete.
- **Command Line**: The command or script that was executed as part of the automation run.

![](https://cdn.document360.io/87d11426-6b1f-4b19-b593-b71e55a81af3/Images/Documentation/image(136).png?sv=2026-02-06&spr=https&st=2026-11-08T16%3A44%3A26Z&se=2026-11-08T17%3A44%3A26Z&sr=c&sp=r&sig=ELKH4Yp6k3Ttmj%2FP5lGa8Xaiu10YSQLMo6gjRaAu6R8%3D)

## Collection Extension History

**Collection Extension History** (**Resolve** > **Tools**) shows a chronological record of Collection Extension runs for the selected endpoint. It helps admins verify what was executed, when it ran, who or what triggered it, how the user interaction was handled, and whether the run succeeded or failed. You can filter by time window and result count to quickly investigate recent activity or troubleshoot past runs.

The Collection Extensions History view presents data in a way that is nearly identical to Automation History. For a full description of all columns, see the [previous section](/documentation/docs/actions-tools#automation-history). Here are a couple of key differences between the views:

- Scope of runs: Collection Extensions History lists Collection Extension executions.
- Primary label: The first column is labeled Collection Extension instead of Automation.
- Columns shown: Collection Extensions History hides automation-specific details (notably command-line/execution details that are shown for automations).
- Availability: In Resolve, Collection Extension history is not shown for macOS and Linux endpoints, while Automation history remains available there.