Errors and error reports (Administration → Errors)

In short. When something breaks, Agora records it in Administration → Errors, grouped by failure. If you allow it, the Agora team receives it too so it gets fixed. Nothing sensitive is kept or sent.

What is captured #

• Server: errors of a page, an action, startup; of the site database, the game database, the license server and Discord.
• Members' browser (in-game tablet included): "This page could not be displayed" screens and uncaught errors.
• Failures that used to go unseen: a notification that could not be written or purged, an MDT attachment that could not be removed from disk, a settings read or a dealership diagnostic that failed, a lost write to the administration log are now noted here (areas notifications.write, notifications.purge, mdt.fichiers.remove…), with a limited rate so the screen is not flooded.
• FiveM resource (1.9.9 or newer): the resource's Lua errors, server side and client side. The same error is sent at most once every 10 minutes, with at most 10 reports per minute, of which only one per minute per player for client errors: two modified clients cannot drown out the real errors (resource 0.3.1 or newer).

Read the errors #

Administration → Errors (administrators only; a badge shows new ones):

1. Filter by Source (Server, Browser, FiveM resource), Severity, Status, Area and Period.
2. Open a row: you see the number of repeats, the first and last time.
3. Each occurrence shows the stack trace, what happened just before, the context and the member involved (link to their page).
4. Mark the error Seen, Resolved or Ignored. A resolved error that comes back goes back to New. The page shows who set the status and when ("Status set by … on …"), which helps when several administrators share the screen.

If the database does not answer, the screen says "The error list is unavailable right now (database unreachable?)" instead of showing an empty list.

Errors are kept for 30 days (5,000 occurrences at most).

What is never kept or sent #

Passwords, tokens, cookies, secrets, license keys, connection strings, forum post content, application answers, 911 descriptions, IP addresses. Emails are masked (j***@example.com).

In what goes to Agora, the member involved is only designated by an anonymous reference: the team sees that two errors affect the same person, never who.

Send the reports or not #

Administration → Configuration → Security, Error reports block:

• Send error reports to Agora (on by default, recommended during the testing phase);
• Do not send: nothing leaves your installation, including what was still waiting. Errors stay visible on your side.

The Send queue shows what is waiting, sent, abandoned (24 h without success) or local. A server that is not running in production never sends anything.

Report one error to Agora ("Report to Agora") #

Independently of the setting above, an administrator can report one error by hand: open it in Administration → Errors, pick the occurrence and click Report to Agora. You see a scrubbed preview of what will be sent (the error, up to 50 lines of context before it, the version, the panel, your tier), then Send to Agora gives a support ID and a Discord direct message with an Open the ticket button (fallback: /ticket open id:<ID>). At most 10 reports per day per installation; the ID expires after 30 days. Full details: Report an error to Agora.

And with support #

When you open a ticket, give the area, the date and, if a member saw it, the reference code. See Where to find the reference code.