ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

Behavior of MODIFY_SYSTEM and queues


Article ID: 227715


Updated On:


CA Automic One Automation


How does MODIFY_SYSTEM() work with queues and exceptions?
Does it override a limit set by an exception?


Release : 12.3

Component :


This depends on when the MODIFY_SYSTEM command is done.  Here is how this breaks down:

  • MODIFY_SYSTEM before an Exception starts:
    The MODIFY_SYSTEM settings from the script will take effect UNTIL the Exception starts, then the Exception will take over.  When the Exception ends, the Defaults will be put back into place

  • MODIFY_SYSTEM after an Exception starts but before the exception ends:
    The Exception settings will be in place until the MODIFY_SYSTEM settings from the script are run.  When the Exception would normally end, the Defaults will be put back into place

  • MODIFY_SYSTEM after an Exception ends:
    The MODIFY_SYSTEM will stay in place until another Exception starts or another MODIFY_SYSTEM command is run

Some of this is also explained in the documentation here:

"Changing the status of Queue objects (Start/Stop) using this script element (Action: MODE) has the effect that the new status is valid until a new modification is made. Modifications to priority or maximum queue slots remain valid until these values are changed due to an exception or if a user changes them manually, see Considering ERT in Queue Objects."