Current pace on Blaze

[icyfirevon]

I have been using the Surge for a year and I run with it on a weekly basis, I love it!! I love that it has built-in GPS which I know the Blaze doesn't have and also the Current Pace data with KM notifier. 

I ran with the Blaze with Connected GPS and I selected Secondary Stat as my Current Pace but this data was no where to be found on the Blaze when I run. There's a much higher number beside a 'clock' icon on the bottom of the watch which is not my current pace in km/h that was tracked and logged on the FitBit app.

Where is CURRENT PACE

If there's no Current Pace on the Blaze, then it is of no use for any runners. Please advise on how this function can be activated properly just like how the Surge has? I had a Live Chat with Fitbit Support and they were not able to help and advised that their engineering team needs to look into it - am I missing something here to activate that feature?

Note: I have Connected GPS on, that is why I was able to see my route and pace/km as the summary on the Fitbit app after I run. But that pace/km was no where to be found on my Blaze while I was running, I scrolled through all the numbers and I only had Elapsed Time, Avg Pace and Distance. Where is current pace on the Blaze? Please help!!! 

Moderator edit: format

[Jason212]

I think the pace is the smaller number at the bottom from what I can tell and from the exercises I have done it seems to be how many minutes/seconds your pace is for 1 mile.  I have not used a Surge so I don't know how it showed the pace.

[mcrmama]

I discovered that and wondered if it is showing pace in miles instead of km perhaps. It seems about right on the splits in km and if you choose average pace instead of current pace, that seems to be about right as well. I suspect something is not converting when we switch to metric on certain data fields.

[icyfirevon]

Thank you! I did check the avg pace option while running but that is an overall avg pace so if I have picked up the pace in the last km, it will not be accurately showing it on the screen for me to know whether I have hit my target speed or not for the last stretch because it would be an average number.

Why would the Avg Pace be shown at a different conversion as the Current Pace - I really hope Fitbit fixes this as they had it perfectly programmed on the Surge and I do love how much lighter and slimmer the Blaze is! 

[icyfirevon]

The Fitbit app summary shows my pace by km in km/h so I'm not sure why it is showing it in miles/min even when I changed the measure to km/h on settings, this is confusing as I have always tracked by km/h and their Avg Pace and Current Pace are shown at different units right now during my run.

[MauriceB]

Still the same pace display problem s after the update. Why is it so

hard to improve?

[The_Lion]

The pace is always min/km. Speed is km/h. So the pace is shown as min/km. During my runs the current pace is shown on my Blaze.

[Rich_Laue]

@MauriceB just saying that you have a display problem without saying what the problem is, gives little clues to help you out.

[Belle123]

trying to locate my pace while running

on my fitbit blaze

[The_Lion]

Workout - Running. Tap on the gear and then choose what to see in the second line. 

[Rich_Laue]

@icyfirevon durring the run, you can swipe through the different stats on 5he Blaze. You can choose avg pace or current pace. Current pace tells you exactly that, it is your pace right now.

[Rebelle]

How i do for tout change my avg