Run recovery mixing up minutes and seconds

I just tested it, and it worked as expected. Are you sure you entered the time correctly?

In my test it looks like this before saving:

And like this after the saving:

Thanks for your answer. Here is the same test as yours:

Before Saving:

After saving:

... anyway, the distance estimate is rather unimportant in this case. What is important is the duration. Test it on the watch, and see whether the recovery step takes 1m20 or 1h20

See image:

It seems the time is picked up correctly the issue is the recovery pace is way to high

You sir are right. This solved the issue in question. A bit more clarification in that field would be nice though

I’ll also add that if you leave that field blank (I’ve never filled it in), Connect seems to use your average running pace for the last little while (apparently the same pace it uses for the Insights page).

(Others have noted that in the Reports page, Connect doesn’t seem to calculate average running pace quite right - it just takes the unweighted average pace over a certain number of activities, as opposed to weighting by distance. As far as I can tell, Connect does the same thing - use an unweighted pace average - for the purposes of Insights and workout estimates.)