Use this article when an automation fails, does not run, or does not show where you expect it. It lists common causes, the automation error codes, the user approval codes, and problems with Assist, manual runs, and Self-Help.
Common Causes of Automation Failures
Check these common causes when an automation fails:
Permissions to run the automation are not set correctly.
Dependent automations weren’t uploaded.
The timeout was set too short. Increase the Runtime Limit of the automation. See Create Automations.
The configuration hasn’t been updated on the system. Run Read Configuration at Configure > SysTrack Settings > Administration.
The Action isn’t enabled. See Enable or Disable an Action.
Relative paths are different, because the action runs in the folder of the Action, where all its scripts are uploaded.
IMPORTANT: Starting from version 11.7, relative paths no longer work for User-context scripts. Use absolute paths or registry-based resolution to load SysTrackPS.dll. For details, see Loading SysTrack PowerShell Module in User-Context Scripts.
A user changes a script directly on the agent for testing. This does not work, because the agent checks the files of the Action before it runs them, and a changed file no longer matches.
Control is passed to another executable that doesn't return an exit code immediately, so the automation runs until the timeout value is reached (examples: SCCM repair automations, debug via Process Monitor).
Behavior differs between 32-bit and 64-bit environments and processes. On 64-bit Windows, the Windows agent runs actions as a 32-bit process. To run 64-bit PowerShell, start the script with a launcher batch file, as ReturnCodeSample.bat does in Automation Examples.
Environment variables may be different when SysTrack runs the action.
On Windows, processes that an action starts are ended when the action ends or times out. To keep a process running, see Keep a Process Running After the Automation Ends.
Automation Error Codes
Code | Definition |
|---|---|
0 | No error |
1 | Failed To Run indicates that the system encountered an error while attempting to run the Action. |
2 | Failed To Run As User indicates that the user encountered an error while attempting to run the Action. |
3 | Failed To Unpack indicates an error unzipping the Action. |
4 | Failed To Authenticate indicates the Action could not be authenticated. |
5 | Failed To Prompt indicates an issue prompting the user. |
6 | Failed To Notify indicates an issue notifying the user. |
7 | Timed Out indicates that the Action ran too long and the Agent terminated it. |
8 | Not Found indicates the Action does not exist on the system. |
9 | Unsupported indicates that the system does not support the Action. |
Engagement - User Approval
Code | Definition |
|---|---|
3 | The user declined the prompt. |
4 | The user approved the prompt. |
Automations Not Listed in Assist
If an automation does not show in Assist, check these settings:
The Action of the automation is approved and enabled at Configure > Tools > Automations and Collection Extensions > Action Governance.
Make available in Assist is selected in the automation.
One of the groups of the user has permission for the automation. Assist and Resolve show only automations that a group of the user is allowed to use. Add the group with Edit Permissions. See Edit Automations.
The system has read the configuration that contains the automation.
For the checks on the endpoint and on the master server, see Automations Not Listed in Assist.
Unable to Manually Run Automations
A user can't run automations manually in Assist or Resolve, and an access denied error says that the rights of the user do not include Resolve.Run Tools Manually or ServiceNow access. The same automations can work for other users or run correctly from a sensor.
To fix it, turn on Run Tools Manually under Resolve in the App Features of the group of the user, in Manage Group Features. For the steps, see Unable to Manually Run Automations.
Self-Help Does Not Show Fix Options
Self-Help does not show the Remediate or Fix It options for an automation, although the automation runs and its sensors trigger. Check these causes:
Make available in Self-Help (Windows Only) is not selected in the automation. Availability in Assist and Self-Help is set on the automation.
Actions that require arguments can not be used with automations that are published for Self-Help. If you provide an optional argument, that automation will not be available in Self-Help.
The Action of the automation is not approved and enabled.
For more causes and checks, see Self-Help Solutions Do Not Show Remediation or Fix Options.