Seeing “Last Sync: 3 Days Ago” at the top of the WHOOP app means your WHOOP 5.0 sensor has stopped transferring data to your phone, even though it may still be recording heart rate and movement on your wrist. In most cases, your recent sleep, strain, and recovery data are still buffered inside the sensor and have not been lost. The fastest way to clear the stall is to charge the sensor, reset the Bluetooth link cleanly, and let the app finish its catch-up transfer in the foreground.
Quick Answer
Charge your WHOOP 5.0, force-close the WHOOP app, toggle Bluetooth off in your phone’s full Settings menu for 15 seconds, and reopen the app while keeping your screen awake. Do not erase or factory-reset the sensor—your strap holds multi-day buffered data that will upload once the connection resets.
Device and Signal Snapshot
- Device: WHOOP 5.0 sensor and WHOOP companion app (iOS and Android)
- Symptom: App displays “Last Sync: 3 Days Ago” (or similar multi-day delay), missing recent sleep or strain cards
- Data risk: Low if you keep the sensor charged and avoid wiping it; high if you run an erase or factory reset before the backlog uploads
What Is Actually Happening
WHOOP 5.0 does not need a constant live phone connection to collect biometric readings. When your phone is out of range or disconnected, the sensor stores raw heart rate, heart rate variability, and motion packets locally in onboard memory until it reconnects.
When that “Last Sync” timer climbs to three days, the sensor is usually still recording, while one of three bottlenecks is blocking delivery:
- A frozen BLE data channel: Your phone’s Bluetooth settings may still show the WHOOP sensor as connected, while the specific Bluetooth Low Energy (BLE) data service has stalled.
- Background app throttling: Aggressive battery optimization on Android or Low Power Mode and disabled background refresh on iPhone can stop the WHOOP app from maintaining long catch-up transfers.
- A stalled multi-day catch-up queue: Once a backlog grows to 72 hours of continuous sensor packets, transferring and processing everything takes longer. If your phone locks or drops Bluetooth halfway through, the sync resets and the “Last Sync” label never updates.
How to Tell Which Problem You Have
Check your WHOOP app’s Device status banner and your phone’s Bluetooth menu to narrow down the cause:
- Phone Bluetooth shows “Connected,” but the WHOOP app stays at “3 Days Ago”: The radio link is active, and the BLE data service or app cache is jammed.
- The app shows “Disconnected” or keeps searching without finding the strap: The Bluetooth handshake itself is broken, or the sensor’s battery dropped too low to maintain the link.
- The app starts “Data Catch-up,” then freezes or loops back to “3 Days Ago”: A large transfer queue is timing out when your phone sleeps, or a cached upload packet is stuck.
What to Do First (Without Losing Your 3 Days of Data)
Start with steps that reset the transfer path while keeping your sensor’s local memory untouched.
1. Charge the Sensor and Disable Phone Low Power Mode
Slide your battery pack onto the WHOOP 5.0 so the sensor has plenty of power for a heavy multi-day upload. At the same time, turn off Low Power Mode (iPhone) or Battery Saver (Android) on your phone, since power-saving modes throttle Bluetooth throughput and suspend background tasks.
2. Run a Clean Bluetooth Reset and Foreground Sync
- Force-close the WHOOP app completely from your recent apps switcher.
- Open your phone’s full Settings > Bluetooth menu (do not just tap the quick-control icon), switch Bluetooth Off, and wait 15 seconds.
- Turn Bluetooth back On, open the WHOOP app, and wait on the home screen.
- Set your phone screen timeout longer temporarily—or tap the screen occasionally—so the phone stays awake and unlocked while “Data Catch-up” runs. Multi-day uploads often stall if the phone locks mid-transfer.
3. Fix a “Connected” but Frozen BLE Channel
If your phone’s Bluetooth menu insists WHOOP 5.0 is connected while the app refuses to move past “Last Sync: 3 Days Ago,” the BLE GATT data channel is stuck. Follow the reset sequence in Why Your Wearable is “Connected” but Not Syncing: The BLE Service Reset before trying more drastic resets.
What to Check If It Still Won’t Sync
If a clean Bluetooth toggle and awake foreground session don’t clear the backlog, work through these deeper recovery steps without erasing the strap.
Reboot the WHOOP 5.0 Sensor
If your app can briefly open Device Settings > Advanced, tap Reboot Device. Restarting the sensor clears its communication controller without deleting stored biometric logs. If the sensor won’t respond in the app at all, follow WHOOP “Sensor Disconnected”: The 3-Reboot Protocol for Recovery.
Unstick the Catch-Up Queue and App Cache
When three days of buffered packets choke the app’s local queue, clearing the app’s temporary cache (without deleting your login or wiping the strap) often frees the transfer. See How to Clear the App Cache for Oura, WHOOP, and Garmin Without Deleting Data. If you see the sync bar stall partway through, “Data Catch-up” Stuck: How to Sync 48 Hours of Missing WHOOP Data walks through getting multi-day backlogs over the finish line.
Force a Bluetooth Bonding Reset
If your phone and WHOOP 5.0 have mismatched security keys—common after a phone OS update—you will need to forget the WHOOP sensor in your phone’s Bluetooth list and re-establish the link inside the WHOOP app. Follow How to Force a Bluetooth “Bonding” Reset for Oura and WHOOP carefully so you re-pair without wiping your sensor data.
Fix Background Permissions so the Stall Doesn’t Return
Once your data catches up, keep the app from stalling again:
- iPhone: Make sure Background App Refresh is turned on for WHOOP; see How to Fix Background App Refresh Blocks on iOS 26 (Missing Watch Data).
- Android: Set the WHOOP app’s battery usage to Unrestricted and keep Nearby devices permission allowed; see Why Your Smartwatch Disconnects When Your Phone Screen Turns Off.
When It’s Actually a Hardware or Firmware Problem
Take your WHOOP 5.0 off your wrist for a moment and check the sensor LEDs. Certain light patterns signal a hardware fault or firmware lockup rather than a phone sync issue:
- Solid red LED: Indicates an internal sensor fault; check WHOOP 5.0 Solid Red Light: Troubleshooting Internal Hardware Failure.
- Alternating red and white LEDs: Indicates corrupted or stalled firmware; follow WHOOP 4.0/5.0 Red & White Alternating Lights: The Bricked Firmware Fix.
If the sensor refuses to pair on a second test phone or shows hardware error lights after charging, contact WHOOP Support for a diagnostic check or replacement.
Bottom Line
Keep your WHOOP 5.0 charged, run a clean Bluetooth reset, and leave the WHOOP app open on an unlocked screen to push the buffered data through—save any device erase option strictly as a last resort after exhausting sensor reboots and bonding resets.