Troubleshooting the Conflict Checker PropertyIssue Conflict checker is not working properly, even after property "change.conflict.refresh.conflicts" is set to true. Symptoms may include the following: Conflict checker not working properly after the change in Property.Property "Run conflict detection automatically after changes to Configuration item, Planned start date, Planned end date or State when a change request is updated" is not working.Property "change.conflict.refresh.conflicts" is not applied even after setting the value to true.Check Conflict is not working. CauseFlush cache is not done after the change in property, which has not applied the property changes.ResolutionTo clear cache: type cache.do in the navigation filter and press enter (OR) https://<your-instance>.service-now.com/cache.do in the URL. System properties contain configuration information that is typically static and doesn't change frequently. Whenever a system property is added or modified, the cache is cleared to synchronize all nodes in the cluster. However, this cache flush can be resource-intensive and may cause an outage if it's done excessively. To avoid such outages, it's recommended not to use system properties to store configuration information that changes frequently (more than once or twice a month). Instead, use a custom table to store regularly changing configuration information.