Actions: Tools

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

• Administrator Actions

• Run Automations

• Run Collection Extensions

• Run 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

An automation is a template that can be executed on the focus system. Automations can be configured to run automatically when a sensor is activated. They can also be run manually from the Run Automations tab.

Automations are set up in Configure. If no automations appear on this tab or you want to create more automations, you must first set them up in Configure. Contact Lakeside Support for assistance.

Run an Automation

To run an automation, follow these steps:

1. Go to Resolve.

2. Select the system on which you want to run the automation.

3. Select Tools from the left menu (under Actions).

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.

6. If applicable, enter any parameter values in the Parameters section (on the right).

7. Under Execution, make a selection in the Run Mode field, and click the Run button.

The Run Modes do the following:

• Run Silently causes the action to run without notifying the user.

• Prompt sends the user a notification that the action is about to run. The user can accept or decline the action.

  NOTE: You will not be notified if the user declines the action.

• Notify sends a notification that the action is about to run without giving the user the option to accept or decline the action.

  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

• 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 system or application that triggered the run.

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

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