Tracking run not properly tracking.

[Gbagukv2]

I start a run on the fitbit app, ensuring it is syncing with the watch. When I finish the run and it tries to log it, two things happen:

1. it creates a log of the run for the next day, so if I ran on a Tuesday it creates a log dated on Wednesday; very odd! in this log the map of my run is recorded and somehow the duration but nothing else (pace, calories, steps, etc)

2. it creates a log with the correct date and time which includes tue analysis of my heart rate and steps but does not show pace nor it attaches the gps map to it. 

what is the issue here?

[RicardoFitbit]

Hi @Gbagukv2, welcome to the Community Forums!

Thanks for bringing this to my attention and for the details that were shared with me. To better assist you with this, can you please let me know if you're using the Fitbit Blaze to track the run exercise or the Fitbit app? If you're using the MobileRun feature, which mobile device are you using? When was the first time you experienced this and how many times since then? 

I'll be waiting for your reply so we can move forward with this.

[Gbagukv2]

1. I have started to experience this issue since 2 weeks ago.
2. I track with the phone (to record the map) but I make sure phone and
watch are in sync before starting the run.
3. The watch I own is a blaze and my phone is an iphone 6s
4. It always creates 2 logs:
1. One with the map, dated for the future! (next day) and no
other data on it (eg pace, calories etc missing)
2. One with no map or pace but dated correctly and with estimates
of calories, steps and heart rate.

Thanks
Miguel