Running cue split time error. Please fix it.

[SunsetRunner]

 Ok, so I'm convinced this is an error that someone has made in the running exercise program, and it would be very easy to fix - literally minutes.  Some people have mentioned it on other threads, but I haven't seen a response from Fitbit yet.  When I'm running, I set the watch to cue every half mile, which it does, BUT, it displays the current running pace while the cue is displayed, rather than the average pace for that split (which my Surge does).  I'm convinced that this isn't what would have been intended by whoever designed this feature.  Does anyone think the way it works at the moment is more useful?  I can't imagine anyone would.

[racertempo]

Yes, it is a mess.  It appears that the split is a literal snapshot of that second, not the average pace over that half mile. 

This is a major issue for a fitness focused watch.  How could this be so overlooked and not even get a reply from Fitbit? 

Here is picture proof:

The obvious pace should be 16'36"

[Mikegillett]

So, I actually have this problem with the app. It only shows the cues, which I have set for about .4k. The app used to also show me the km/mi splits. I keep asking about it, but have only got a “ we are working on it.”

[CharlesJ]

I have the same problem.

[racertempo · Accepted solution]

So I think the new Firmware has fixed this problem.....can anyone else verify as it looks like it worked great for me today after the update.

[Mikegillett]

I’ll give it a try!  Thanks for letting me know it worked for you!

[thitzeman]

Verified this has been fixed with the latest software update. On my run this morning, the previous mile pace was displayed rather than the current pace. 

[CharlesJ]

My split time is also working now.