Something is not working, what should I do?

Try these first

1. Hard refresh with Ctrl/Cmd-Shift-R. Resolves stale-JS or cached-CSS issues most of the time.
2. Different browser or private window. Rules out extensions blocking something.
3. Check the URL. If you reached the page from an old link in an email or a document, the route may have changed.
4. Sign out and back in. Resolves session edge cases.

Use the bug button

Every signed-in page has a small Report a bug button at the bottom right corner. Click it, describe what went wrong, and submit. The current page URL and your username are auto attached. We see new reports in the admin within minutes.

What to include in a bug report

The more specific, the faster we can fix:

• What you tried to do (e.g. "open the race plan for my A race").
• What happened instead (the error message, a missing panel, a button that did nothing).
• When (rough time, so we can correlate with server logs).
• Browser and device if it is a visual or interactive bug.
• Whether it is consistent (every time, or once?).

Ask a how-to question instead

The bug button is for "something broke". For "how do I do X" use Ask a question. We turn common questions into new help articles.

Response times during beta

We aim to reply within 1 to 2 business days. Concerning bugs (data loss, sign-in broken, billing wrong) get same-day attention.

Known gotchas

• Multi-file devices can split a long ride into two FIT files. Look for both in your device export.
• Time zone drift can shift an activity to the wrong day if your device clock was off. Open with a wider date filter.
• Old Garmin Connect exports sometimes ship a different TCX variant that loses HR data. Re-export from your device directly as FIT.