The Triggered Action Settings (for Autopilot) is available from the settings of DriveWorks Autopilot.
Triggered actions will not be run if they are released from an Embedded Child Specification. You should control the specification flow of the Child Specification from the Parent Specification if the Child needs to be Transitioned.
Enabled by default, this setting allows triggered action documents (applied in DriveWorks Administrator) to be processed by DriveWorks Autopilot.
To enable or disable triggered action processing:
Load balancing is the ability to process tasks across multiple DriveWorks Autopilot machines.
Load balancing ensures that when a task is picked up to be processed by one DriveWorks Autopilot, then another DriveWorks Autopilot will not try and process the same task.
Load balancing is only supported on Shared Groups.
Tagging is the ability to target DriveWorks Autopilot to process a specific task.
See Autopilot for more information.
The number of times Autopilot will retry execution of a triggered action before flagging it as failed and moving on to the next action.