The session is yours. The choice should make sense.
You have logged a few sets on your phone. Somewhere along the way, the copy saved to your account and the copy on the device stop agreeing. A recovery screen appears. It asks which version you want to keep, but gives you almost nothing useful to decide with. After a hard session, remembering the exact sequence of every save is a lot to ask.
That was the problem behind our latest workout recovery update. The screen needed to explain what each copy contained. Both choices also needed to work: choosing the local session should preserve the latest work on that device, including activity recorded after the recovery screen first appeared.
Compare the work, then the timestamp.
Hyperion now puts the device and server copies side by side. Each shows its completed, non-skipped sets, recorded workout time and actual saved timestamp. Guided intervals appear when they are part of the session. The comparison highlights a copy with more logged sets and a copy saved more recently as two separate facts.
Imagine the server has 12 logged sets and your device has 10. That is a useful reason to inspect the server copy. But your device might contain a correction to a weight or an exercise note. A later timestamp can also reflect an edit rather than extra training. Neither more sets nor a newer save proves that a copy contains every change you care about.
A clear choice needs a reliable result.
Keep this device saves your current local work over the server copy. Use server version replaces the device's unsynced edits. The screen explains those consequences beside the actions, so the decision does not depend on understanding how workout sync works underneath.
We also corrected the case where newer guided activity could leave the local choice stuck behind a stale-state error. Recovery now settles that activity and reads the latest saved work before applying the choice. An older retry cannot bring back an upload that the recovery decision has already replaced. If a session has already finished, local sets can continue as a separate workout while the finished record stays intact.
Small messages matter during a workout.
The same release brings pause and save messages into the flow of the workout. Personal records sit beside the sets they relate to. Longer workout names wrap within a compact header. Together, these changes keep useful feedback close to the task without covering the session in floating messages.
Android 1.0.16 (18) was submitted to the existing closed-testing track on 15 October 2026. At the time of this note, Google review was pending. Recovery was checked in browser tests and in a signed Android build, including keeping local work and restarting the app. Wider device testing continues as part of the beta.
Explore the app behind the story.
Meet Hyperion