When we have multiple event rules, then the binding by last rule must overwrite binding executed by previously running rules.DescriptionWhen we have multiple event rules, then the binding by last rule must overwrite binding executed by previously running rules. Below are the 4 use cases when we have two event rules with expected behaviour:1. 1st rule is SUCCEEDED to bind - 2nd rule FAILED to bind - The Alert must not be bound2. 1st rule is SUCCEEDED to bind - 2nd rule SUCCEEDED to bind - The Alert must be bound by 2nd rule3. 1st rule is FAILED to bind - 2nd rule FAILED to bind - The Alert must not be bound4. 1st rule is FAILED to bind - 2nd rule SUCCEEDED to bind - The Alert must be bound by 2nd rule Steps to Reproduce In below scenario's, alert binding was not overwritten by last rule. Below are the some cases where we observed incorrect behaviour: 1.Event Rule 1 CI Field Matching - Succeeded to bindEvent Rule 2 CI Identification - Failed to bindExpected: Alert is NOT boundCurrent: Alert bound by 1-st rule2.Event Rule 1 CI Identification - Succeeded to bindEvent Rule 2 CI Field Matching - Succeeded to bindExpected: Alert bound by 2nd ruleCurrent: Alert bound by 1-st rule3.Event Rule 1 CI Identification - Succeeded to bindEvent Rule 2 CI Field Matching - Failed to bindExpected: Alert is NOT boundCurrent: Alert bound by 1-st ruleWorkaroundCurrently there is no workaournd for this issue and please check problem record PRB1892804 for permanent fix.Related Problem: PRB1892804