Diagnostics

Diagnostics sits at the bottom of the right rail, apart from the other entries, with a badge counting what it has to report. Red means errors, amber means warnings, no badge means nothing went wrong.

It is a builder tool. It never appears on a published map.

What it records

Four kinds of event:

• network, the requests your map made to fetch tiles, features and styles;
• MapLibre errors, raised by the rendering engine itself;
• console warnings;
• runtime exceptions.

Each record shows its level, its category, the message, where it came from and, for a network request, the HTTP status and the URL with its query string stripped.

Reading it

The counters at the top double as filters: click errors to see only those, click total to come back.

Two more actions help when you need to go further:

• Copy JSON puts the whole log on your clipboard, which is what to attach if you report a problem.
• Clear empties it, so you can retry an import and see only what that attempt produced.

Log all network requests starts recording successful requests too. It is off by default because logging everything slows the map down, and it does not backfill: only requests made after you turn it on appear.

When to open it

Open Diagnostics when something does not look right and the map says nothing: a layer that stays empty, a basemap that never draws, an imagery source that worked yesterday.

The usual answers are visible here. A refused request means the provider blocks browsers, in which case adding the same service through Data can relay it. A 404 on a tile means the source moved. A style error means the layer loaded but could not be drawn as asked.

You can also hand the problem over: the AI Assistant reads these diagnostics, so asking it why a layer is not loading gives it the same evidence you are looking at.