What I have identified is that the policy has different sid in both clusters and they aren't synchronized.
Release : 9.2
Component : API GTW ENTERPRISE MANAGER
Different sids on different nodes implies thatthe customer could be using 2 different mysql db instances (considering that its still a cluster environment).
In which this issue is expected, if that is the case, then customer can delete one of the policy from one node, and then allow the replication to take place (ssg restart), and then see the sids, after replication sids should remain the same and hence achieves synchronization. This should resolve the problem.
Other policies are not having this problem, since most probably they are replicated and share the same sids. If there are other policies that are also sharing different sids, then they should apply the same solution.
If that is not the case, can we know more details about their cluster environment, like how dbs and nodes are linked?