Automation Collisions

Automations are defined as colliding when a system or business CI is involved in more than one automation over the same period of time.

Automation collisions are calculated based on scheduling conflicts. If two or more automations share a common element, and their scheduled start and stop times overlap, these automations are considered to be colliding.

Two automations taking place at the same time do not necessarily have an effect on each other. Collisions occur only if they involve at least one common CI. There are two types of collisions:

  • Direct collision. Occurs when two or more automations directly affect the same CI.

  • Indirect collision. Occurs when one of the automations indirectly affects the same CI. For example, if an automation involves increasing the memory on Server A, Server A is directly affected. If Application B is connected to Server A, and is not directly involved in the automation, it is only indirectly affected by the automation.

Note The collision type is determined by the highest severity level of the impacted CIs.

For information about viewing collision details, see Automation Analysis > Collisions Pane.