ACTIVATE_UC_OBJECT can be used to create a recursive call leading to endless loops.
Document ID :
Last Modified Date :
Show Technical Document Details
CA Automic Workload Automation
CA Automic Workload Automation:Release:12.0
CA Automic Workload Automation:Release:12.1
CA Automic Workload Automation:Release:12.2
, the script function
could be used to take advantage of a '
' to make
, which when implemented poorly would often lead to
This was corrected in the versions
Automation Engine 11.2.7, 12.0.4, 12.1.1 and 12.2.0
To prevent endless loops in the Automation Engine, the number of recursive object activations is limited.
16th attempt to activate an object is canceled
with the status FAULT_OTHER and the error message
' (RunID '
') is interlaced too much.
The limit also applies to recursive workflow activations or a mix of workflow activations and object activations.
Example: A workflow activates a script which in turn activates the workflow again. If the loop happens 5 times (3 times 5 is 15), the 16th activation is canceled.
This correction means that when upgrading to one of the above mentioned versions or higher, all objects taking advantage of this 'bug' must be redesigned.
Misuse of the script function ACTIVATE_UC_OBJECT to make recursive calls can leads to endless loops.
The recursive call check logic for the script function ACTIVATE_UC_OBJECT has been enhanced by introducing a new setting to define/deactivate the check for endless loops.
The new setting is called '
' and it can be found in the '
The valid values for the setting are as follows:
Check is disabled
The new setting has been introduced in the following versions:
- tentatively planned release end of January 2019.
- tentatively planned release end of October 2018.
- tentatively planned release end of February 2019.
Was this information helpful?