Overview
This error event means that Automation Workshop was unable to decrement the selected global variable. As a result, the variable's value did not change.
Event examples
See some examples of the Decrement failed Event messages:
- Task "Send Invoices" Action "Decrement Variable" failed due to the file system error for "Mail Template #2" variable. [aw:3]
- Action "Decrement Variable" failed due to the variable "Invoicing" is protected. [aw:2]
- Failed due to the variable "Period 26" was not found.
Cause
There are several possible causes for a failure to decrement a global variable:
- The variable may be protected, preventing any changes.
- The specified variable was not found.
- A file access error may have occurred—such as insufficient permissions, a missing variable file, or a non-existent variable directory.
Solution
If a global variable cannot be decremented, it is likely due to protection settings, missing configuration, or access restrictions. The following steps can help identify and resolve the issue:
- For protected variables, use the Manage Global Variables interface to disable protection on the variable you want to modify.
- If the variable is missing, which may happen when importing Tasks from another system, you can either create it manually in the Global Variables Editor, or use a Modify Global Variable Action early in the workflow with the setting to create the variable if it does not already exist.
- If the problem is due to filesystem issues, verify that the global variables folder is present, properly configured, and that the system has sufficient permissions to access it. See the Hardening Automation Workshop guide for more information on managing access and security.
Need help?
If you have any questions, please do not hesitate to contact our support team.