Reference · Troubleshooting
Fast checks for common problems
Most comp-day issues are one of a few simple failures: wrong page, wrong competition, stale data, or a missing permission. Work down this list before escalating.
Common problems
A judge's passcode isn't working+
Double-check they've selected the correct competition, then re-enter the passcode exactly (it's case-sensitive). If it still fails, reset the judge passcode from the discipline setup page and have judges enter the new one.
An athlete is missing from the leaderboard+
Confirm the correct category and round are selected first. If the athlete is genuinely absent, check the import or startlist source data and re-import or edit there.
A score was entered incorrectly+
Fix it directly from the chief view (/boulder/chief,/speed/chief, or/lead/chief). Cross-link to theFixing mistakes guide for detailed correction steps, then refresh the affected views.
The public page looks outdated+
Refresh the hub and confirm the shared URL slug matches the correct event. Check the publish and freeze state in the Publishing & freezing guide to ensure it isn't locked.
Permissions or access looks wrong+
Sign out and back in to refresh Clerk roles. Confirm the person is using the intended account and the correct organisation.
Poor internet connection during judging+
Keep notes on paper and minimise extra tabs to reduce latency. Re-check scores once the device reconnects — entries queue locally. See theJudges & devices guide for offline handling.
A judge can't find their station+
Confirm the judge selected the correct competition, category, and round. For boulder, verify the detail or group filter matches the active session.
Speed finals head-to-head matches are mismatched+
Use /api/speed/override for deliberate match overrides. For re-climbs, call the climb and update the bracket manually.
The hub won't publish or is stuck frozen+
Refer to the Publishing & freezing guide — it covers setup publishing, auto-publish triggers, and manual unfreeze steps.