Phones die, apps get force-quit, and GPS drops. If your live recording failed, you can still get an official result by submitting your run after the fact — ALLEYKAT replays it through the race course and finalizes your time, indistinguishably from a live finish.
Ways to recover a result
| Method | When to use it |
|---|---|
| Upload a GPX file | You recorded the run in another app and can export a .gpx track. |
| Sync from Garmin | You wore a connected Garmin watch during the race. |
| Sync from Strava | You recorded the run on Strava (or a watch that syncs to it). |
| Submit a past run | The run is already in your ALLEYKAT run history, from another race or a free run you recorded before. |
| Manual time & distance | You have a verified time to submit for a DNS/DNF fix. |
Fix it from the leaderboard
- 01Open the race and find your rowOn the race detail page, tap your own row in the leaderboard.
- 02Choose a recovery methodPick GPX, Garmin, Strava, a past run, or manual entry.
- 03ALLEYKAT replays your trackThe submitted track is validated against the start, waypoints, and finish, and your official time is computed.
Review flags
A self-submitted result that lands in the top 25% of finishers is automatically flagged for the race director to review. This keeps recovered results fair — it's not an accusation, just a check.
What's supported today
- Fixing a result from an in-person race leaderboard — GPX, Garmin, Strava, a past run, or manual entry — is iOS only today. Relay and backyard ultra have no post-race recovery, because a track submitted after the fact can't prove a handoff or per-yard corral presence.
- Submitting a past run as a result into an async or FKT race works on iOS and Android.
- GPX upload covers in-person races; Garmin covers in-person, async, and FKT; Strava covers in-person, async, and FKT.
Note
Garmin auto-sync can also match your activities to open races automatically — see Garmin integration.