---
title: "Common Problems with Actions"
slug: "common-problems-with-actions"
description: "Fix common problems with SysTrack actions: an action missing on the agent, an action that fails to start or run, and SYSTEM actions for users."
status: "update"
updated: 2026-11-05T08:25:28Z
published: 2026-11-05T08:25:28Z
canonical: "documentation.lakesidesoftware.com/common-problems-with-actions"
---

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

# Common Problems with Actions

Use this article when an action does not reach a system, does not start, or does not run as expected. Each section gives the problem, the likely cause, and the fix. For problems with file uploads in Action Builder, see [Troubleshooting Action Builder Uploads](/documentation/docs/create-actions-1#troubleshooting-action-builder-uploads).

## The Action Does Not Show Up on the Agent

When an action does not show up on the agent, the agent has not received the configuration that contains the action, or the action is not approved and enabled.

The configuration must be pushed to the agent. By default this does not happen constantly, but you can push it manually to test it. All automations go along with all configurations, as long as they can run on the system (for example, Windows or Mac). To push the configuration now, run the **Read Configuration** command:

1. In **Configure**, go to **SysTrack Settings** > **Administration**.
2. In the **Operations** panel, select the systems.
3. Under **Command Dashboard**, select **Read Configuration**, and click **Run**.

The action must also be approved and enabled. Check the **Approved** and **Enabled** columns on the **Actions** tab in **Configure** > **Tools** > **Automations and Collection Extensions** > **Action Governance**. To approve or enable the action, see [Approve and Enable Actions](/documentation/docs/approve-actions).

## The Action Launched but Did Not Run as Expected

When an action launches but does not run as expected, the agent log files show where the action started and whether it logged an error. On Windows, the agent log files are LsiAgent0.log to LsiAgent9.log in the agent install folder. The default folder is `C:\Program Files (x86)\SysTrack\LsiAgent\`.

1. Open the most recent agent log file.
2. Search for the name of the automation. The log shows whether an error message was logged when the automation started.

The agent logs these error messages:

| Message | Cause and Fix |
| --- | --- |
| An attempt to start Command [Automation Name] failed with error code: [Error Message] ([Error Code]). | The agent could not start the script. The error message and the error code give the reason. |
| An attempt to start Command [Command Name] as User failed. Running Commands as User is not supported on this system. | macOS and Linux agents run commands only as System. Set **Run As** to **System** for the automation. See [Edit Automations](/documentation/docs/edit-automations). |
| Command [Automation Name] is running longer than expected and will be terminated. | The automation ran longer than its runtime limit. Make the **Runtime Limit** of the automation long enough. See [Edit Automations](/documentation/docs/edit-automations). |

Other messages usually contain details about the error.

## An Error Occurred While Launching the Action

When an error occurs while the action launches, and the agent log files (LsiAgent0.log to LsiAgent9.log) do not explain it, check these causes:

- The logs show that the action started, but it stops at random points. Another tool, such as an EDR security tool like Carbon Black or Falcon, can block the action. Ask the team that manages the tool to allow the action.
- The action uses relative paths. On Windows, from SysTrack 11.7, an action that runs as User runs from a temporary folder in the user profile, so a relative path to another folder can break. See [Loading SysTrack PowerShell Module in User-Context Scripts](/documentation/docs/loading-systrack-powershell-module-in-user-context-scripts).

## SYSTEM Actions for Users Are Not Working

When SYSTEM actions that must interact with the user do not work on Windows, the cause is the Windows job object. The processes that an action starts are part of a Windows job object. All processes in a job object must run in the same session ID, so an action that runs as System cannot start a process as another user without breaking out of the job.