Upload failed

An upload failure means the track didn't make it from the device to the cloud. The Android app will retry automatically, but here's how to diagnose and fix persistent failures.

Android app — track shows "Failed"

1. Open ⋮ → Sessions.
2. Tap the failed session.
3. Tap Retry upload.
4. Watch the status — if it moves to Uploading and then Synced, the problem was a transient connection issue (common if the upload tried during a handover between Wi-Fi and mobile data).

If it fails again immediately, continue below.

Check your connection

Upload requires a working internet connection. Check that:

• Wi-Fi or mobile data is on and connected
• You can load a web page in your browser while the upload is retrying
• The connection isn't behind a captive portal (some hotel/event Wi-Fi networks require you to accept terms in a browser before internet traffic flows)

The app doesn't use special ports — if normal web browsing works, uploads should too.

File size and connection speed

A one-hour session recorded at 1 Hz (the default) is typically 100–400 KB after compression. This should upload in under 10 seconds on a normal connection. Very slow connections (below ~100 kbps) may time out on larger files — try again on a stronger connection.

Import page upload failures (FIT, GPX, etc.)

If uploading via app.dinghy.coach/import:

"File not recognised" — the format wasn't detected. Check that the file extension matches the actual format (.fit for Garmin FIT, .gpx for GPX, etc.). If the file was renamed, try renaming it back to the correct extension.

Progress bar stops and doesn't complete — this is usually a connection drop mid-upload. Refresh the page and try again.

"Upload failed" message — check your internet connection and try again. If the problem persists on a good connection, check the browser console for error details (press F12 → Console tab) and contact support with the error shown.

The file is corrupted

If the Android app shows a session as Corrupted, the recording file was damaged — this can happen if the phone ran out of battery while writing the file, or if storage was full. Corrupted sessions can't be uploaded. The file is kept locally in case partial data is useful, but there's no way to recover the full recording.

Retrying after a long delay

The Android app retries failed uploads automatically with increasing intervals (exponential backoff). If a device was offline for days, uploads will resume automatically when it next connects. You don't need to do anything — just make sure the app is installed and the device connects to internet at some point.

If you want to force an immediate retry, open the Sessions screen and tap the session to retry manually.