Need help during a live meet?

Before Publishing

• Confirm local backend health at the manager console.
• Verify Cloudflare Tunnel status for the public API.
• Check that the active meet database and lanes are correct.
• Open the public results URL from a separate browser or phone.

Data Corrections

Published race data comes from the meet operator. Send correction requests to the competition desk or organizer responsible for the active meet.

Useful correction details include meet name, event number, heat, lane, swimmer name, team, posted time, expected time, and whether the change affects placement, podium display, or team scoring.

Race-Day Checks

If spectators cannot see current data, confirm that the local backend is running, the selected meet is active, the tunnel is connected, and the public browser is not holding an old cached app. A hard refresh usually resolves stale client assets after a new Cloudflare Pages deployment.

Support Scope

LiveResultMeet support covers public result delivery, dashboard access, operator setup, API health, print layout, and production deployment checks. Official result decisions, swimmer eligibility, event schedules, and timing corrections remain with the meet director or competition desk.