There are two scenarios to consider.
- Most of the (hopefully few) times the connector breaks, it breaks because of the downtime of a system: Infor, Xero, Stellarise, DNS or internet itself. In this case, the connector can't even perform the longest task: data collection. This means the next time the connector successfully run, it will just override the data previously collected or partially collected.
- If the connector breaks in the process itself, then the next time it will reprocess all of the same data: both the one that has been already processed and the one that has not. Anyway, by design, both Xero and InforLN should have been implemented following the "INSERT OR UPDATE" pattern.
Regarding the UPDATE part of the equation, there are edge cases where for example InforLN can launch an exception like "Payment already processed" or Xero can say "It is not possible to update paid invoices". In each of the cases though, all of these exceptions and messages are collected and reported in the Audit table.