To reduce such conflicts avoid updating the same records at the same time, or decide that some records are maintained on one server while others on the other. If you make changes to a record but cannot see the data update on the other - trigger replication between the servers and then refresh your pages on the target server to see the latest data.
When conflict occurs, such records do not show in the normal resource views on the Door Tablet Web UI or the Door Tablet client App. The impact of this is that your licences may be consumed in "dead" records which you do not have access to.
Conflict discovery in the add-in
From V5.3.140 (28 December 2019), the Door Tablet server add-in resolves this issue for you as follows: