Blaze not syncing Run exercises

[AlessFitbit]

Fitbit Update: 7/6/17

 Yesterday, there was a fix released that resolved this issue. Now that I have confirmation that this was resolved, I'm going to close this thread. If this pops up again in the future, please create a new post to report the issue. 

Thanks everyone for your patience! It is always appreciated. 

Fitbit Update: 6/29/17

Thanks everyone for your patience while this was being investigated. Our team was able to identify the problem, however, I don't have a timeline for when the fix will be released. Once the fix is released I will update this thread again. 

---

Fitbit Update: 6/14/17

Some Blaze users have reported that their run exercises initiated on the tracker are not syncing over to the Fitbit app or web dashboard. 

Our team is aware of this issue and currently investigating the root cause. Thanks to all who have reported this. I will post any updates on this thread when there is more information available.  

[sendme]

Possible solution??

I had the same issue as just about everyone else -- My steps and other data were synced to my phone, but my runs wouldn't.  

They are now!

Here's what I did -

Usually I don't to with my phone, therefore don't pair my Fitbit and phone.  

This time I paired my phone and Fitbit. And after the run they synced AND my past runs and walks all appeared.  

Certainly worth a try. 

[Elizabeth1211]

Just today I emailed asking (1) when we can expect a fix - meaning an actual timeline and not just a "we're working on it" and (2) if it is not able to be fixed, what the company plans to do to go about sending refunds. No reply yet but I'm curious to see if I will get the same canned response, as it appears I asked a similar question.

[Bellalove22]

It's such a bummer! I called customer service today, they are working on
the problem.

[SunsetRunner]

@Rich_Laue What are you saying I'm using to track my run if I'm not using my Blaze? I don't understand your comment! As for no-one is saying my tracker is faulty...Fitbit have just e-mailed me to say that it is isolated to my Blaze and a new tracker will not have the same issue and are looking to replace it. I'm not convinced as I know the issue is not isolated to my Blaze. As for the connected GPS workaround A) I shouldn't have to take my phone and B) It makes no difference, the Run still does not sync! 

[DarloJo]

Still no luck with mine, after uninstalling/reinstalling everything. Really disappointed. I'm not prepared to use my phone to track runs as a workaround - why spend money on a Fitbit in the first place?!

[Colinm39]

Please direct me with some thoughts on the Non phone use of the Blaze.  I'm trying to see what the issue is and I realise my findings won't help those posting in this topic. Probably makes it all the more difficult for Fitbit Engineering  when some of us have no issues @AlessFitbit  @Rich_Laue

I have the 2 x original issue of the Blaze in February 2016 and I cannot get them to fail on Walk, Run, Hike and Cycling.. even Workout etc.  It all syncs perfectly.

Today's tests range from 11 minutes to 44 minutes.. Is there a minimum time difference, a level of activity etc...because it still works if I do illogical things like set Cycling and only walk around the house.. Still synced just now.

Blaze Firmware 17.8.401.3, Android Sony XP V7.1.1... Not on the compatibility list, but everything works.. Except the Exercise tracking (MobileRun) on the App V2.51. Pausing and Resume on the Connected GPS always fails.  Pause and Finish always works.

[Blakey66]

I found that if I just start the run exercise manual start on the blaze and then stop after 15 seconds it syncs. If I start the manual run and actually go for a 20min run then review the summary before scrolling down to select done, it does not sync. What I do see after the run is that it registers it as one of my 5 active days with zero minutes in the summary. I’m not sure if its a syncing issue or the Blaze no longer holds the data before syncing.

Update - Just used the stopwatch function today hoping the auto run would recognise it so at least I could time my run. Stopwatch worked well but not run recognised. In fact nothing recognised!! This however may be a syncing issue as now I cannot get my phones bluetooth to recognise it, so of course it will not sync. Tried removing it from my bluetooth settings but I cannot not find it to re-link it. Looks like my Blaze is dying slowly as is my patience with Fitbit! 

I've now had to remove it from my account and add it again. Now its synced and the auto run is showing. So this is a possible work around, just use as a stopwatch and let the auto run function record it. No good though if you want to know any other data during your run, but ok for the odd 5km park run!!

[Colinm39]

@Blakey66Thanks for getting back so quickly.. That is another test I can do, but it's approaching  midnight here, so tomorrow we will test again...

I will ensure I scroll through the results before I tap All done and sync.

---

@Blakey66 wrote:
I found that if I just start the run exercise manual start on the blaze and then stop after 15 seconds it syncs. If I start the manual run and actually go for a 20min run then review the summary before scrolling down to select done, it does not sync. What I do see after the run is that it registers it as one of my 5 active days with zero minutes in the summary. I’m not sure if its a syncing issue or the Blaze no longer holds the data before syncing.

---

[kazoshay]

Yep mine logs it as exercise and shows Run in the dashboard but has 0
calories, no steps, no other data. I should add that I jog without my
phone on me so I don't sync until I get back home and by then I have
already stopped the exercise on my watch and reviewed the results and hit
"Done" This worked fine for the first 2 months of using my Blaze then
abruptly stopped working over the last month I think.

[Bellalove22]

I asked them as well!

They don't have a timeline as to when we can expect a fix, she said they
are currently working in it. She seemed confident that the problem will get
resolved. I asked what if it doesn't, what then and wouldn't that deem
their product to be defective? She said given that the feature was apart of
their product they will be able to restore that feature. Soooo now I wait.
Lol

[AlessFitbit]

Thanks everyone for your patience while this was being investigated. Our team was able to identify the problem, however, I don't have a timeline for when the fix will be released. Once the fix is released I will update this thread again. 

[Rakesh3073]

Great

Sent from my iPhone

[ReddyFox]

Thank you so much.

Sent from my iPhone

[Cara.Dante]

I, too, run without my phone. (I'm a minimalist - the least amount as weight as possible.) I'm finding my Blaze is inaccurate in the distance it is measuring/recording. And by a significant amount. My first clue was my split times. Then I looked at the distance recorded and headed over to a few sites (Endomondo, gmap-pedometer) to check if I had miscalculated the route(s). My Blaze is shorting me 1/3-1/2 mile.

I've only been using the Blaze for a week and a half, so I am not terribly attached to it. But I wish it would work better. I can still return within the nest 2 weeks, so I hope they have a fix.

[Rich_Laue]

If you want to run without your phone and its connected gps you will need to set your running stride leangth. Why? Because your tracker is unable to measure distance.  Instead it counts your steps then multiplies them by your stride to come up with aproxamate distance.  Http://Www.fitbit.com/?q=stride

[Colinm39]

@Cara.DanteYou must ensure your stride lengths are accurate if you only use the Tracker to record your runs without the phone. If not Fitbit uses your this default setting.  We don't know what they use for running.

Male:  Height (in inches) × 0.415 = Estimated Stride Lentgh (in inches)

Female:  Height (in inches) × 0.413 = Estimated Stride Length (in inches)

Also you have to be confident that you are getting close to 100% steps. If you set your stride to "Auto" and you use the Exercise tracking on the phone App for at least 10 minutes it will use your GPS distance and divide that by the steps on the Tracker to give you your stride.  See this link

I then manually alter the stride to use the Auto settings that the GPS/Tracker calculated. This should take away the issues with your gait, arm swing etc and give a reasonable result.  Fitbit only tell us their trackers are within +/- 5%

I concurrently used MapMyRun and MobileRun (Exercise tracking) and had no issues, both reported a distance within tolerance. Don't use Connected GPS via the Blaze. Too many issues as reported elsewhere

---

@Cara.Dante wrote:

I, too, run without my phone. (I'm a minimalist - the least amount as weight as possible.) I'm finding my Blaze is inaccurate in the distance it is measuring/recording. And by a significant amount. My first clue was my split times. Then I looked at the distance recorded and headed over to a few sites (Endomondo, gmap-pedometer) to check if I had miscalculated the route(s). My Blaze is shorting me 1/3-1/2 mile.

I've only been using the Blaze for a week and a half, so I am not terribly attached to it. But I wish it would work better. I can still return within the nest 2 weeks, so I hope they have a fix.

---

[AZWeedWacker]

I have experienced the same issue with non syncing of the run activity. The odd thing is that right after I did my run I did Yoga and it tracked and synced just fine.

I contacted support in regards to this issue as well as several questions I have in regard to the use of the fitbit, specifically the audio cues that are set up in the app and can only be started by the app, which then you do not see anything on your watch in regards to the run. I have copied the entire email exchange for all to benefit and hopefully for the developers to see and improve upon.

We appreciate the time you're taking to let us know your concerns about the two issues you're experiencing with your Fitbit Blazes run and voice cues features. By the way, thank you for letting us know the functions of the devices that are convenient for runners like you. We're constantly striving to improve our Fitbit products and services, and we appreciate all of the input we receive from our valued customers.

Upon checking our system, we could confirm that the last time your tracker recorded your run data was on June 24th, 2017 at 6:40 AM and Yoga at at 6:32 AM on Wednesday, June 28, 2017. Since this is an abnormal behavior of your tracker, our team was able to identify the problem, nevertheless, we don't have a timeline for when the fix will be released.

When it comes to your concerns about the voice cues feature setup, we recommend you to visit our Fitbit Community, which is the best place to make your voice heard is the Ideas board on, where our product development teams consult regularly to ensure we're delivering on what our customers need and want. Please take a moment to visit and give us your feedback. 

If you find that a similar suggestion has already been made by another member of the community, you can vote for their idea and add your comments. Our product team looks forward to reading and incorporating your suggestions into future versions of Fitbit trackers and apps. 

Thank you so much for your feedback and for participating in our community!

We appreciate the time you're taking to let us know your concerns about the two issues you're experiencing with your Fitbit Blazes run and voice cues features. By the way, thank you for letting us know the functions of the devices that are convenient for runners like you. We're constantly striving to improve our Fitbit products and services, and we appreciate all of the input we receive from our valued customers.

Upon checking our system, we could confirm that the last time your tracker recorded your run data was on June 24th, 2017 at 6:40 AM and Yoga at at 6:32 AM on Wednesday, June 28, 2017. Since this is an abnormal behavior of your tracker, our team was able to identify the problem, nevertheless, we don't have a timeline for when the fix will be released.

When it comes to your concerns about the voice cues feature setup, we recommend you to visit our Fitbit Community, which is the best place to make your voice heard is the Ideas board on, where our product development teams consult regularly to ensure we're delivering on what our customers need and want. Please take a moment to visit and give us your feedback. 

If you find that a similar suggestion has already been made by another member of the community, you can vote for their idea and add your comments. Our product team looks forward to reading and incorporating your suggestions into future versions of Fitbit trackers and apps. 

For the developers... Seems as though this software program between phone and watch is an issue with the apple platform as well. If you guys can figure out how to allow the controls and cues to work by utilizing just the watch with the phone working in the background, you would be heroes! Lets see if you can beat apple to the punch on this hardware software integration issue!

[JIM.NJ]

Blaze will not sync run data, and it is frustrating. Currently running wearing two watches, one being a watch Fitbit was supposed to replace. Please fix problem or Fitbit will be returned as defective! 

[Delasoul99]

Seriously .... So do you think this will fixed before the end of the year ? 

[JIM.NJ]

My Garmin watch has worked just fine for years. I just thought the fitbit Blaze was an upgrade because the chest strap isn't necessary, but If it doesn't work as advertised why keep it.