My workout disappeared
A session you logged is missing. Most of the time, the data is still on the device or one tap away in a backup file. Here is how to find it.
You finished a heavy set, hit the rest button, locked your phone, and never heard the bell. Three settings cause this, and all three are quick to fix. Run the checks in order. The timer will fire on the next set.
The rest bell rides on a local notification. If notifications are off at the system level, the bell never reaches you.
On iOS, open Settings, tap Notifications, scroll to Rackd, and confirm Allow Notifications is on. Sounds and Banners both need to be enabled. Critical Alerts is not required and is not used.
On Android, open Settings, tap Apps, find Rackd, then Notifications. Confirm All Rackd notifications is on, and that Rest timer (or Workout) channel is enabled with sound. Some Android skins (Samsung One UI, Xiaomi MIUI) ship with a separate Battery setting that suspends background notifications. Allow Rackd to run in the background and skip battery optimisation.
Open Rackd, start a fresh set, tap Rest, lock the phone. The bell rings at zero.
Focus modes silence local notifications too. Even with notifications enabled, DND or Sleep Focus blocks the rest bell from making sound.
iOS: Control Centre, Focus, confirm DND and Sleep are both off. If you train at the same time daily, add Rackd to the allowed apps list inside the Focus you train under. That way DND can stay on for everything else.
Android: pull down the quick settings tile and toggle Do Not Disturb off. If you use Bedtime Mode or a custom schedule, add Rackd to the exception list.
Pixel and Samsung devices both honour app exceptions inside DND. The bell rings, the rest of the world stays quiet.
Some Android devices kill background timers aggressively, especially after a system update. If notifications and DND check out and the bell is still silent, run the workout with the screen on.
In Rackd, open Settings, then Workout, and turn Keep screen on during workout to on. Place the phone face-up between racks. The rest timer counts down on screen and the bell fires from the foreground, where no battery saver can interrupt it.
If the screen-on fallback works and the locked-screen bell does not, the device is suspending Rackd in the background. Disable battery optimisation for Rackd in system settings, and the bell returns on the next session.
Three settings, three minutes. Back to work.
A session you logged is missing. Most of the time, the data is still on the device or one tap away in a backup file. Here is how to find it.
Phone says 225, tablet says 220. Sync is the fix. Check it's on, run a manual sync, and let the newer record win.
Sign-in to Rackd web access failed on Google or Apple? Here is the short list of fixes that clears it 95% of the time.