Troubleshooting

Get back on track

Start with the symptom and follow a short, ordered checklist before repeating work or contacting support.

Choose the guide matching what you see. Each checklist starts with the quickest checks and explains when you have reached a useful stopping point.

ProblemStart here
Slow reps, missing reps, no estimated 1RM, app language, or minimum OS versionFrequently asked questions
Encoder or Speed device is missing, will not connect, or disconnectsConnection troubleshooting
Recorded workout is missing or still waiting to saveFind a missing workout
Feature, menu, athlete, or coach action is unavailableCheck access
No reps, extra reps, wrong velocity, or unexpected 1RMCheck measurements
Scheduled workout is absent or on the wrong dayCheck scheduling
Cannot sign in, verify email, or accept an invitationAccount and sign-in
Audio, settings, units, exercise selection, or a page behaves unexpectedlyApp and settings
Labs is empty, filtered incorrectly, or showing a different calculationLabs troubleshooting
A device is broken, damaged, or malfunctioningReport a broken or faulty device
Order status, invoice, delivery, or a defective or missing itemReport an order or shipping problem
Paid plan missing, expired, or due for renewalActivate or renew your subscription
You have checked the relevant steps and need helpContact support with useful details

Three context checks solve many problems

  1. Organization: the workspace in which the program or data lives.
  2. Athlete: your active person or coaching selection.
  3. State: planned, active, finished, or pending upload.

A calendar prescription is not a saved result. A connected device is not necessarily the active recording device. A created athlete profile is not necessarily a registered login. The task guides explain those distinctions as well as the fixes.

Preserve unsynced work

If today’s session is missing, check the original recording device before signing out, clearing storage, or reinstalling. Look for an active workout or Pending workouts, and save a pending JSON recovery file when necessary.

On this page