Conflict resolution and the Conflict Log
What happens when two terminals change the same thing offline.
When terminals that were offline reconnect, IBEX reconciles their changes with fixed rules. Routine cases are handled silently; the genuine ambiguities the rules could not settle are listed in the Conflict Log, so nothing is lost without a trace.
- Open Manager → Conflict Log.
- Review the Unresolved entries after a period when terminals were offline together.
- Check each one against the bill, then Resolve it with a note.
Note
In normal use, with one till per order, conflicts are rare — the log is there for the edge cases. If the log cannot be read — offline, or when the read fails — it says This could not be read. Check the connection and try again. with Retry, and reads by itself once the connection is back; it never shows the all-clear, or an empty list, for a log it has not read. A Resolve that fails says why.
Was this article helpful?