Connected GPS Pace data cutoff

[SunsetRunner]

 I track my workouts using a Fitbit Blaze. During the last leg of my runs, whenever I reach a certain point at a distance about 5.75 miles, the GPS will cut out and the there is no data for GPS until I reach the very end. Is this some problem with how much can be recorded in the Blaze?

[Kait5991]

Does this happen no matter where you run? Or is it the same place every time? Maybe you don't have service for that part of the run? 

[SunsetRunner]

I don't know if it's a reception cut problem, the part where it cuts off is where I go to start running, and I get no problem there in the beginning. Next time I run I'll take a slightly different path and see if the Blaze still gives gimmicky tracking bugs. 

[SunsetRunner]

So I ran again around a different place with slightly more distance. 

 The results were mostly good but like before, near the end when I'm doing like the last .4 or .5 miles my heart rate will be recorded and such but the pace info will be almost completely gone until the last second when I end the workout. I dunno if It's a memory limit with the Blaze, but I guess It's gonna have to be a shortcoming I'll have to work around. I wonder if this problem will get bigger once I try to run more than 6 miles such as 7. 

[SunsetRunner]

Okay after more current updates, the problem associated with Pace data cut-offs seem to have been fixed. Yay, thanks Fitbit.