Find and Filter Error Reports

This how-to narrows the Error Reports list down to the failures you care about, exports them, and marks them as resolved once they're fixed.

Prerequisites

• Error reporting added to at least one call path in your game's code (see Report Errors from Your Game), and at least one failure reported by a player running that build.

Filtering Reports

In the Web Console sidebar, open Moderation and select Error Reports. The list shows every report for the current game, newest first. The filters above the list combine, so you can narrow a large list down to a single player's failures on one endpoint.

The following filters are available:

• Player ID: the player's ULID. Use this when you already know exactly which player hit the problem, for example from a support ticket.
• Player Public UID: the player's short public identifier. This is the value a player can read off their own profile, so it's usually the one they can give you themselves.
• Endpoint: the API path the request was made to, such as /v1/.... Use this to see every failure against one feature.
• Status Code: the HTTP status the API returned. Filter to 500 for server-side failures, or to a 4xx code to find requests your game is sending incorrectly.
• Status: whether reports are open or resolved. Defaults to All reports.
• From and To: the reported-at date and time range. Use this to scope the list to a specific build release or incident window.

Each of the Player ID, Player Public UID, and Endpoint fields has its own Search button to apply that filter.

The list shows the status code, HTTP method, endpoint, player, resolved state, and reported-at time for each report. Click a row to open the full report.

Exporting Reports to CSV

Click Export CSV above the list to download the reports currently shown.

Note

Because reports are only retained for 7 days, exporting is the only way to keep a record of a failure beyond that window. Export before an incident's reports age out if you need them for a post-mortem.

Resolving a Report

Open a report and click Resolve once you've fixed the underlying issue. Resolved reports stay in the list, marked Resolved, so you keep the history of what went wrong. If you resolve something too early, click Unresolve on the report to reopen it.

Use the Status filter to hide resolved reports and keep the list focused on failures you haven't dealt with yet.

To remove a report entirely rather than mark it resolved, click Delete on the report.

Caution

Deleting a report is permanent — it removes the payload you would need to debug the failure or hand to support. Prefer Resolve unless you're certain you no longer need the report.

Conclusion

You've filtered the Error Reports list to the failures you're investigating, exported what you need to keep, and marked the fixed ones as resolved. To make sense of what an individual report contains, see Understanding an Error Report.