Inconsistency in Conflict Detection Display: Embedded List Empty Until Form RefreshedIssue Following conflict detection, in certain states, the embedded list for conflicts appears empty. However, upon refreshing the form, the conflict list is once again visible. In essence, the conflict list does not reload automatically, and requires the user to either click the check conflict button or refresh the form.ResolutionThis is an expected behavior. Conflict detection is influenced by the size of the Configuration Management Database (CMDB) and the complexity of its relationships. As the CMDB grows in size, conflict detection takes longer to complete. Furthermore, it is not possible to make conflict detection synchronous. Given the complexity of the process and the amount of data that needs to be traversed, it is not advisable to make conflict detection synchronous.Related LinksImportant Points to note: "Update Conflict" Business rule creates the conflicts asynchronously in the system using a worker. BR is scheduling a worker for Conflict detection.Now, as the worker is running async with the change request transaction, we can see the conflicts after some time on the form. Also, If the advanced mode conflict is also Activated, Affected CIs are also considered during conflict detection, which makes conflict detection even slower. Whenever a conflict detection happens, the current Conflicts are re-evaluated if they are still there or not.