FAQ & troubleshooting

Seeding & entries

Seeding refuses to run — “max events exceeded.” A swimmer is entered in more events than the league cap allows. Remove entries until they’re under the cap, or — if the referee has approved an exception — use Seed anyway to acknowledge the violations and proceed.

Re-importing reshuffled nothing — is that right? Yes. Seeding is deterministic, so re-importing the same data produces the same heats and lanes.

A heat has only one swimmer. Seeding consolidates lone-swimmer heats into an adjacent heat automatically. If you’re seeing one after hand-edits, re-check the event’s heats on the schedule — moving the swimmer yourself with move/swap is the lightweight fix; re-seeding works too but discards any results already entered for re-seeded events.

An imported roster row didn’t show up. Check the roster review queue — ambiguous matches (similar name, changed birthdate) wait there for you to bind, create, or dismiss. See Rosters & participants.

On deck

Times aren’t coming in. Check the timing-status indicator on the run screen: is the deck agent / console connected? The recent-updates log shows what’s arriving.

A time looks wrong (pad vs. backup). The app flags pad/backup disagreements on the affected lane — accept the corrected time, promote a recorded button time, type a manual time, or dismiss and keep the pad time.

A swimmer showed up after their event was seeded. Use a deck entry or a fill-in from the run screen — see Handling changes on deck.

“Refresh and try again” when I save. Someone else changed the same heat/event (optimistic locking). Refresh to pick up their change, then redo yours.

Email

Invites aren’t sending. Confirm SMTP is configured, SWIM_PUBLIC_BASE_URL is set, and the recipient is allowed (SWIM_EMAIL_ALLOWLIST). See Email setup. The token is always returned even when the email is skipped, so you can copy the link manually.

Still stuck?

Search these docs, or open an issue on the project’s GitHub.