Common Errors with Automations

Here are some common errors to avoid:

Permissions to execute are not set correctly.
Dependent automations weren’t uploaded.
The timeout was set too short.
The configuration hasn’t been updated.
The Action isn’t enabled.
Relative paths are different since all scripts will be uploaded to the same folder.
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.
User tries to change a script directly on the agent for testing. This will not work as the signatures will no longer match.
Control is passed to another executable that doesn't return an exit code immediately so automation runs until the timeout value is reached (examples: SCCM repair automations, debug via Process Monitor)
Difference of behavior due to 32-bit / 64-bit environments and processes.
Environment variables may be different when SysTrack runs the action.
Processes started from an action, in PowerShell, are terminated when the action completes.

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.

Code	Definition
3	User opted for Not Now.
4	User opted to continue.