What each running app can restore after a lost run
Short answer
Whether a lost run can be recovered depends on where it was lost, not on which app you use. A run that reached a vendor's servers and was then deleted is often recoverable through that vendor's own tools, while a run that was never saved never left the phone, and Strava states in its own help centre that such an activity cannot be restored. Only what a vendor publishes about itself is worth acting on, so every row here is either a quotation with a date or is marked as not documented.
Not every lost run is lost in the same place. A run that reached a vendor's server and was then deleted is a different problem from a run that was finished but never saved, and only one of the two has a documented recovery path. Work out which of the two you have before you try anything. Everything below is either a quotation from a vendor's own help page with the date it was fetched, or a statement that nothing could be obtained.
The three places a run can be lost
Two of them are on your phone. They are ordered here by how far the run got toward the server.
- On the phone, unsaved. The recording ended, or the app died, and the activity was never written into the app's saved list. Nothing was sent anywhere, so no vendor tool can reach it.
- On the phone, saved but not uploaded. The activity exists inside the app and is sitting in an upload queue waiting for a connection. This is the case most often mistaken for a lost run, and it is the one you can usually fix yourself.
- On the server, uploaded and then deleted. The vendor holds it, or held it recently, and this is the only case where a restore button is likely to exist at all.
The order matters because the first hour of panic usually involves logging out and reinstalling, and that is the single action that destroys case two while doing nothing for the other two.
What Strava documents, quoted in full
Only Strava states the never saved case plainly. No other app here has a published statement about activities that were never saved. The Strava article How to Restore a Deleted Activity, fetched 2 August 2026, states it twice.
If you record an activity on the Strava app, click finish, but don't save it, it is never sent to the Strava servers and, therefore, cannot be restored.
Strava Help Center, How to Restore a Deleted Activity, fetched 2 August 2026
We cannot restore activities that have not been saved or manual entries that have been deleted.
Strava Help Center, How to Restore a Deleted Activity, fetched 2 August 2026
Read that as a description of phone recording in general, not as a complaint about one app. A vendor can only restore what its servers received.
Uploaded then deleted, which is the recoverable case
Strava can bring back exactly two kinds. The same article names them: "Activities uploaded from a 3rd party device and then deleted" and "Activities created from the Strava mobile app 'Record Screen' that were saved and then deleted". It describes a Recently Deleted tab on the Strava website, reached from My Activities under the Training menu, that holds activities deleted within the last 30 days, with a Restore option on the far right of each row, fetched 2 August 2026.
It is a website tab, so looking for it in the phone app will not find it.
Checking the phone before you touch the app
Assume case two until you prove otherwise. Leave the app installed and stay signed in. Runkeeper puts that in its own uninstall guide, in bold, before any of the steps.
If you get a notification saying you have an unsaved activity or activities, don't log out!
Runkeeper help, How to safely uninstall or reinstall the Runkeeper app on iPhone, fetched 2 August 2026
Every app hides its pending queue somewhere different, and none of them put it in the feed you normally look at. The table below records what each vendor's own pages said on the day they were checked.
One case looks like a lost run and is not one.
Runkeeper's article on missing history puts a second account first among the causes: "Check the 'Settings' menu in the phone app, and look at the email address listed there. If that's a different address than what you're logging into the website with, that's why your activities are not visible in your account." Before concluding anything is gone, check which address the app is signed in as, per Runkeeper's missing history article, fetched 2 August 2026.
| App | What the vendor's own page says | Status on 2 August 2026 |
|---|---|---|
| Strava | An unsaved activity "is never sent to the Strava servers and, therefore, cannot be restored". For activities that did save, the syncing article describes retrying from Pending Uploads or Unsync'd Activities, and on Android exporting a stuck upload "as a .GPX file to your phone's internal storage" for manual upload from the website. | Fetched: restore article and syncing article |
| Runkeeper | Activities that have not reached the servers carry "red warning triangles" next to them in the activity list under the Me tab. The guide's own resend instruction is "Scroll to the bottom of the Summary screen > Tap 'Edit' > Save activity", and it says to do that before uninstalling and not to log out while any exist. | Fetched: uninstall guide |
| MapMyRun | Un-synced workouts "are stored in the app settings until you have a strong data connection", listed under app settings then "Unsynced Workouts", and an activity missing from that list "you will have to manually log". The article's closing note is the one that matters here: "If the app is uninstalled/reinstalled, any un-synced workouts will be lost." | Fetched: Syncing Unsaved Workouts, read through the help centre's own article endpoint after the HTML page returned HTTP 403 |
| adidas Running | Not quoted here. Nothing about unsaved or unsynced activities was retrieved. | Not documented here: the Runtastic help centre returned HTTP 503 to every request, article pages and article endpoint alike |
| Nike Run Club | Not quoted here. An article on this exact question exists and its page loads, but the answer text is assembled by JavaScript after load, so only the title came back. | Title only: Why Didn't My Run Sync to the NRC App? returns HTTP 200 to a browser style request and HTTP 403 to the fetcher used here |
The platform health store as a second copy
Only saved runs get copied. A workout in Apple Health or Health Connect is a copy of an activity the app saved, so it rescues a sync failure and a mistaken deletion, not a run that was never saved. The copy may sit there even when the app's own list looks empty.
Whether the copy exists at all comes down to a permission you granted at some point. Apple's own description of the Health app is that "Apps must request the ability to read data from or write data to your Health app" and that "All third-party apps must explain why they are requesting access to your Health app data", per Apple's Health app privacy page, fetched 2 August 2026. An app that only reads from Health has written nothing for you to recover.
On Android the equivalent is Health Connect, where a run is an exercise session and the track is a separate record. The documentation states that "Exercise routes allow users to track a GPS route for associated exercise activities and share maps of their workouts with other apps", and lists what each point in a route carries: time, latitude, longitude, horizontal accuracy, vertical accuracy and altitude, per the Health Connect exercise routes guide, fetched 2 August 2026. Writing a route needs its own permission separate from writing the session, so a session can survive with no track attached.
Practically: look in Health under workouts, and in Health Connect under exercise, for the date in question. A session with no route still gives you a start time, a duration and usually a distance, which is enough to log the run manually and enough to show support that it existed.
Nike Run Club, and what could not be verified
Nike's answer text never came back.
No statement about Nike Run Club appears on this page, because none could be read. Nike does publish an article on exactly this question, Why Didn't My Run Sync to the NRC App?, and that address returns HTTP 200. Its answer text is assembled by JavaScript after the page loads, so a fetcher that reads only the delivered HTML gets the title and nothing else, and the same address returned HTTP 403 to the fetcher used here on 2 August 2026. The adidas Running help centre returned HTTP 503 the same day to its article pages and to its own article endpoint alike.
A page that will not open to a fetcher is not a vendor with nothing to say. Open that Nike article in a browser on your own phone and you will get an answer this page cannot print. What the failures mean is only that nothing quotable was captured here, so those cells stay empty instead of being filled in from memory. MapMyRun is the counter example worth noticing: its help page returned 403 as well, and the same help centre served the article in full through its own article endpoint, which is why that row carries quotations and the other two do not.
Apply the same test to any advice you find about your own app, including this page. If a claim about what an app can restore is not traceable to that vendor's own words, it is somebody's guess, and acting on a guess in the first hour is how a recoverable run becomes an unrecoverable one.
What to do in the first hour
- Do nothing destructiveDo not log out, do not uninstall, do not clear the app's storage or app data in system settings, and do not delete the failed upload yet. Anything waiting to sync lives inside the app's own storage and goes with it.
- Look for the queue, not the feedThe activity feed is a list of what reached the server. The pending queue is somewhere else: Pending Uploads or Unsync'd Activities on Strava, a red warning triangle beside the activity on Runkeeper, app settings then Unsynced Workouts on MapMyRun. Find the queue before you decide the run is gone.
- Get a real connection and retryMove to WiFi or a strong signal and retry the upload from that queue. Strava's own syncing article also suggests recording and saving a short new activity, which can push a stuck upload through behind it.
- Check the platform health storeOpen Health or Health Connect and look for a workout at that time. A second copy there is often enough to reconstruct distance and duration even if the original never uploads.
- Export before you delete anythingIf the app offers a file export for a failed upload, take it first. Strava documents exporting a stuck Android upload as a GPX file to internal storage, which can then be uploaded from the website. A file on disk beats a queue entry you are about to clear.
- Then contact the vendor, with specificsDate, start time, approximate distance and duration, phone model and app version. Do this while the queue still exists. After a reinstall there is nothing left for anyone to look at.
How to make the next long run safer
Recovery cannot be made reliable after the fact. The useful work happens before the run, and three questions separate apps whose worst case is a few seconds from apps whose worst case is the whole session.
- Does it write the track to storage during the run, or hold it all in memory until you press save?
- If the app restarts mid run, does it offer to continue the same activity, or does it start a new one and leave the first half orphaned?
- Where does your history live: phone, server, or both?
Runflake answers the first two.
Read them as mechanics. They are not promises. After a crash the app rebuilds the run by replaying the raw points, steps and events from its database instead of trusting the stored summary, so a summary row that is out of date does not cost you distance.
When it restarts and finds an unfinished run it offers to resume. The card says "You have an unfinished run" with the line "Saved up to where it stopped", a Continue button, and a Hold to finish button that needs a long press so a mis-tap cannot end the run. Resuming keeps the same run instead of starting a second one: new points continue the original numbering, the original start time is kept, and the course, the voice coach and the heart rate feed are switched back on.
The resume offer is not open ended. A run can be continued for 30 minutes after its last heartbeat, and past that it is closed automatically at the next launch and saved with its finish time set to that last heartbeat rather than the moment it was found, so an abandoned session does not turn into a three day run. A run recorded on a watch is handled from the other direction: the phone keeps the watch receiver open even when no run is in progress, because the watch may deliver a backlog days later.
Question three has a blunter answer. Runflake reads run history from the phone's own database, and there is no path that pulls runs back down from the server, so moving your history onto a new phone is not something it does. That is a real limit, and it is better known before you rely on any app for a training block. Runflake is built and is not yet published to the App Store or Google Play, so there is no download available today.
For the mechanics instead of the recovery steps, why running apps lose runs covers what happens on the phone during a run and why the save step is the point of failure. If the same phone keeps losing runs, the cause is usually the operating system rather than the app: see why an iPhone stops tracking a run in your pocket and Android battery settings that stop run tracking.
Common questions
- Can a run that was finished but never saved be recovered?
- No vendor tool can retrieve it, because an unsaved activity was never sent to a server in the first place. Strava states this directly in its own help centre. The only copy that could exist is whatever the app itself wrote to your phone's storage while you were running.
- Is reinstalling the app a safe way to fix a stuck upload?
- It is the most damaging thing you can do at that moment. Activities waiting to sync live inside the app's own storage, so uninstalling, clearing app data or logging out removes the queue along with everything sitting in it. Retry the upload on a stable connection instead, and leave the app installed until the queue is empty.
- Does Apple Health or Health Connect keep a second copy of my run?
- Only if the running app asked for permission to write workouts there and you granted it. That second copy is written by the app at the moment it saves an activity, so it can rescue a sync failure or a mistaken deletion, and it does not help at all when the run was never saved.
- Why are some apps left blank in the comparison table?
- Because their own pages could not be read on the day this was checked, and a blocked or empty page is not the same as a documented answer. The adidas Running help centre returned a server error, and Nike's answer text is drawn by JavaScript so only the article title came back. Filling those cells in from memory would produce exactly the kind of advice this page exists to replace.