Export or back up the relevant data first. Do not delete, void, unreconcile, or adjust historical transactions unless you understand the accounting impact.
Menu names can change. We link current first-party instructions so you can confirm product behavior before acting.
Identify the failure before applying a fix
A connected ecommerce, inventory, CRM, time-tracking, payroll, or reporting app has stopped sending data or is creating incorrect mappings.
Record the complete message, affected organisation or company, user, date range, and last successful action. A precise symptom is more useful than trying several broad repairs at once.
Workflow map
Recover a connected app without replaying twice
Decide which system is authoritative, then narrow the failure before touching the connection itself.
- 1
Scope
Establish whether one record, one mapping, one date range, or the whole connection is failing.
Evidence: An exported failure queue, with IDs and timestamps for one reproducible example.
- 2
Access
Review the app under Xero connected apps and verify the connecting user and permissions still exist.
Evidence: The provider’s status page and support documentation.
- 3
Mapping
Correct the contacts, tax rates, currencies, tracking categories, products, and accounts the failure names.
Evidence: One test record syncing after the correction.
- 4
Replay
Reconnect only if the provider requires it, then replay one controlled batch.
Evidence: Totals reconciled on both sides, with no object created twice.
Checks before changing data
- Name the app, failed record type, error text, and last successful sync time.
- Check whether the user who originally connected the app still has Xero access.
- Decide which system is authoritative for the affected data before editing either side.
Resolution path
- Scope the failure. Determine whether the issue affects one record, one mapping, one date range, or the entire connection.
- Export the failed queue or error log if the app provides one.
- Record IDs and timestamps for a small reproducible example.
- Check Xero permissions and the connection owner. Review the app under Xero connected apps and verify the connecting user and required permissions still exist.
- Do not disconnect until you know how the provider handles queued and previously synced data.
- Check the app provider’s status and support documentation.
- Correct mapping before replay. Review contacts, tax rates, currencies, tracking categories, products, and account codes referenced by the failure.
- Test one record after the correction.
- Confirm the target object was not already created under a different ID.
- Reconnect only when required. If the provider instructs you to reconnect, stop new posting, export the queue, reconnect once, and replay a controlled batch.
- Disconnecting stops new data but may not cancel the app subscription.
- Reconcile totals after the replay.
Verify the result
A disappearing error is not enough. Confirm the accounting and workflow outcome:
- One controlled record syncs exactly once.
- Mappings and totals agree in both systems.
- The failure queue stops growing.
What to avoid
- Repeatedly clicking full resync.
- Editing the same record in both systems during recovery.
- Disconnecting without knowing how queued data and billing are handled.
When to involve product support, IT, or your accountant
Stop making changes and escalate when any of these conditions applies:
- The app has no usable error log or replay control.
- Duplicate financial records have already posted.
- The integration uses custom code or API credentials.
Bring the exact error, screenshots, affected record IDs, timestamps, product version or region, and a description of every change already attempted. That evidence shortens the support path and reduces repeated or conflicting fixes.
Sources checked
First-party product documentation used to verify the workflow and risk notes in this guide.