Symptoms

Volume thresholds for the 2nd installed policy are ignored.

Impact

PEM respects volume threshold from the first evaluated action. Since the policy/rule evaluation order is not deterministic, the first evaluated action is not deterministic as well.

Conditions

When a flow selects two Gx session reporting actions from two different rules with the same application filters and the same monitoring key, but volume thresholds configured from those policies are different.

Workaround

Mitigation: Volume thresholds across rules with the same application and monitoring key when applied to the same subscriber, should be the same.

Fix Information

None

Behavior Change