Common errors and how to fix them

Most error messages in the panel name a specific code. A few patterns come up across many screens:

"Already exists" / conflict (409)

Something you're creating collides with a row that already exists (a duplicate entry, a duplicate name). Check the list for an existing match before retrying — most of these screens tell you which row conflicted.

Access denied (403)

Your role doesn't allow this action for this club, or you're looking at another club's data. Check your role under Members & roles, or that you have the right club selected (sidebar → club switcher).

Not found (404)

The record was deleted, or belongs to a different club/event than the one you're viewing. Refresh the page — most lists refetch automatically and will drop the stale row.

Validation errors (400)

A field is missing, out of range, or in the wrong format. The message names the field; scoring validation errors in particular open a dedicated modal listing every problem row at once instead of one toast per row.

Locked configuration

Some setup (e.g. rating configuration) locks once entries exist, to protect results already scored. This is expected — contact a system administrator if it truly needs to change.

Server error (500)

Something failed on the server. The message includes a correlation id — that's what support needs to look up what happened; the assistant's "Get help from AI" action on the error toast passes it along automatically.

Still stuck?

Use Get help from AI on the error toast (or open the assistant drawer) — it reads the exact error code and whatever the current screen is showing, and can point at the specific fix.