@pavel-samokha Thanks.

@el2thek I think as there is no range shown besides the gauge on top, which by the way was still green if I was faster than the 6:48 pace, the target should show the upper boundary of the range so you know you have to be a bit slower than that.

But yeah I have no clue where the 7:09 target pace is coming from.

@trailcafe OK thanks I will wait then…

@pavel-samokha I’ve done it

@isazi Got it thanks - i had to start from scratch with the process but works now - cheers.

@The_77 I assume you’d better ask Runalyze how they do the sync and to contact Suunto to clarify the differences

@sartoric
thanks!

I use Strautomator for this : if activity not run or trail it’s not on my timeline
You have 3 free automation
https://strautomator.com/feature/commute
I will have a look to activity fix to compare

@HurricaneWeasel there were some backend issues (on Suunto’s cloud) over the weekend. Everything should be working from Sunday on.

Good point. We are working on providing more details in the app regarding the partners.

Thanks

Had the same issue. I think resetting the password (forget password) allowed me to set an actual suunto password.

@David-Brady I had problems Saturday and Sunday, but since yesterday evening everything is okay again. Ambit 3 and Suunto app beta.

Its kinda know and discussed on another hijacked thread of yours @Šón-Čestr 😄

The issue is that strava cannot handle nested laps. We are working on B2B solution for this.

One advice is to turn off any laps for swimming so strava only gets the pool length autogenerated ones

@be1t0n 😞
not yet. Actually, you could continue using MC till next summer

Hey sorry for the late reply. It dont sync with movescount as movescount is going away eventually.

IS that a partner connection the diviac

I think this is a Strava issue and I raised an issue with them. https://support.strava.com/hc/requests/1401815

Hmmm works for me 😮