Runs Stop Automatically after 1km

[SaraF21]

Hi everyone,

I've noticed the last few times that I've started up a run exercise on my Versa, it turns the exercise off after 1km. When I switch it back on, it lets me get to the end of the run but I'd like to keep it logged as one exercise rather than two separate ones - has this happened to anyone else?

Any help greatly appreciated - thanks!

[tbird53]

Hi, 

Same thing happens to me after 1 mile. I have no idea how to change it. I hope someone answers you so we both get the answer. 

[AlejandraFitbit]

It's great to see you around @SaraF21 and to welcome you @tbird53.

If your exercises are stopping, I recommend restarting your Versa by doing the following:

1. Press and hold the back (left) and bottom buttons until you see the Fitbit logo on the screen. This should take less than 10 seconds.
2. Let go of the buttons.

Keep in mind that in the meantime, you can always edit your exercises by following the instructions in the help article How do I edit or delete Fitbit data and activities?.

Let me know the outcome. 

[SaraF21]

Thank you Alejandra. I restarted the Versa and it fixed the problem for a while, but now has reverted to its old ways! Do you know of any other potential fixes?

Thanks again,

Sara

[crw1980]

I'm having the same problem on the Ionic ... My guess is, as some people have it at 1k and others and 1mi that it has something to do with the set notifications per given distance or time. You might try turning those off and it might help but who knows ... It really is annoying

[timg75]

I have had the same issue on three recent runs. Just posting to keep the thread alive and hope that a solution is found.

I’m using an Ionic.

[paula1970]

Yes has happened to me but not on every run just on the odd one or two. Today it did and when I looked at the screen it said it was reconnecting and I pressed the go in the corner. It did record two separate runs but the distance was correct. I ran with my husband who uses Nike app and our distances were the same. A fix would be great for this. Thanks everyone at Fitbit for posting this as with all technology I automatically think it’s something I am doing! 

[21maximillian]

Hey. This still happens to me now on my Versa! Restarting fixes it but it reverts back after a while. It’s an annoying bug.

I know this may be a minor bug to Fitbit but people have been reporting this same problem since 2017! The fact that this still has not been resolved does not reflect well on Fitbit at all. 

[timg75]

Hi. Thanks for keeping the thread alive and adding to the examples of people experiencing this bug.

i have an open ticket with Fitbit support now. I have sent them numerous examples of where this has happened and the .tcx files for the runs.

They seem to have acknowledged the problem and the last communication said they are working on a solution. Let’s wait and see.

In the meantime I will probably do a quick reset before each run which so far has averted the problem. Not a suitable long term solution but at

least a workaround.

[NOLAfan]

It happened to me yesterday.  Versa buzzed at 1 mile (felt it on my wrist).  When I looked at it about ~ 10 minutes later, it had stopped tracking my run.  Restarted it, but lost around 10 minutes of tracking. 

[paula1970]

Thanks for the posting. For me it seems to be happening less frequently now.
A fix however is still required.

Sent from my iPhone

[paula1970]

This is annoying. I have done this several times but it does seem to be better lately for me. I usually run with my phone as well which tracks through the app so at least I haven’t lost tracked runs. It disturbs your running rhythm though to be restarting your Fitbit watch. A fix is long overdue.

Sent from my iPhone

[Devonne]

Wow. I cannot believe that this issue has been occurring since 2017 and no fix hasn’t been made. Just wow. I just got this Fitbit a few days ago. First couple of times during a treadmill run it was fine. Now today I felt it vibrate and when I went to look why it was back on the home screen. Seriously, no one has fixed this issue yet? So very disappointing. Kills my entire run vibe and makes me want to throw this garbage in the trash and get an Apple Watch. FItbit doesn’t take their customers seriously. ALL they ever do is tell your to do a reset as if that’s a permanently fix.

[timg75]

It would be nice to get a Fitbit moderator to comment on this thread. It's been a while since they engaged with it but the problem clearly isn't going away.

Any comment Fitbit?

[21maximillian]

Didn’t happen to me yesterday but happened to me today. The irregularity and unpredictability of this bug makes it even more annoying. 

I wonder how long Fitbit might ignore us. Or maybe they’ll come back and tell us to restart our devices again. 

[paula1970]

Or sell us a new device. #moneymaking

Sent from my iPhone

[NOLAfan]

No over the air flash fix will equal me going back to a Garmin.  

[MarcoGFitbit]

Hello @21maximillian, @timg75, @NOLAfan, @paula1970 and @Devonne, I hope you're doing well, it's nice to see you around the Fitbit Community. 

First of all, I would like to apologize for the delay in the response. As @timg75 mentioned, our team is aware of this issue and they're working towards a solution for it. However, they may not be able to provide a fix in the immediate future. We'll continue to monitor the situation, and keep our team informed of the impact to you and other customers. We understand that this isn't the resolution you're hoping for, but rest assured we're always working to improve our products.

We're sorry for any trouble. We appreciate your patience and look forward to getting you back on track.

Please let us know if you have any other questions.

[Tshaner62]

I was having the same problem, stopped at 1m, reset and now it stops at 5min.  So frustrating, a bug that ruins one of the sole purposes of owning this device.  Please please get this addressed! 

[21maximillian]

I’ve upgraded myself to a Garmin because of this issue that Fitbit does not  show any real intent to fix. 

Been using the Garmin for a few months and have not faced this issue once.

I hope Fitbit fixes this for all of you here!