Avoid incidents for secondary AlertsDescriptionThis feature got introduced in Orlando with the System Property: "evt_mgmt.avoid_int_enabled"More details, here: https://docs.servicenow.com/bundle/orlando-it-operations-management/page/product/event-management/concept/c_EMEventCorrelationRules.htmlIf there is grouped alerts and there are incidents on secondary alerts, we do not want keep the incidents on secondary alert.Steps to Reproduce 1. Configure alert correlation rules to create primary/secondary alerts2. Create alert management rules to create incidents in response to primary alerts only3. Incidents may be created for secondary alerts also, ignoring the alert management rule in 2WorkaroundThere are two separate jobs, each having different invocation interval and not synchronized, therefore the incident may created much earlier than the group becomes secondary, these are the scheduled jobs: 1. Evaluate Alert Management Rules ~11s2. Service Analytics group alerts using RCA ~1m The temporary workaround is to increase the interval of job #1 to be greater than job #2 (but that would not guarantee a full catch)Related Problem: PRB1354364