Downloading and Reading Debug Logs

Debug logs record what the integration actually did, including the errors Xero returned. They're step 2 of the support process because they answer questions no description can.

Where they are

Two routes to the same data:

• Configuration → Help & Troubleshooting → Step 2 — the quickest way to download logs for a support case. Step 1 on the same screen, Create a Diagnostic Snapshot, writes an org summary into the log first
• Configuration → Tools → Debug Log Viewer — the full viewer, which is where you'd actually diagnose something

Reading the viewer

Four counters across the top — total logs, errors, warnings, and how many arrived in the last 24 hours. The last one tells you at a glance whether a problem is current or historical.

Logs are grouped by issue type rather than listed one by one, with a count of how many times each occurred, when it was first seen and when it was last seen. Click a row to expand the individual occurrences.

That grouping is what makes the screen useful: 400 errors is daunting, 15 distinct issue types is a list you can work through.

First seen is often the most valuable column — it usually lines up with a configuration change.

Filtering

Filter by severity, date range, or free text. Download CSV exports what you're looking at, which is easier to attach to a case than a screenshot.

What to look for

• The error text Xero returned — usually the actual answer
• Which record it relates to
• When it happened, to line up with a change you made

Reproduce first

Logs capture what happens while they're on. Reproduce the problem, then download — logs from before the attempt won't contain it.