Generally been having watch problems throughout today. Unfortunately it always tries to sync when I charge it - and if there's any slight server issue it can go wrong, and corrupt a lot of the settings until resynced. It timed out last night so I was being careful to get the GPS located by making it do it several times. This took much longer than anticipated as the first time I gave up after 5 minutes and initiated a new phone sync (another 5 mins) to redownload cache, then wait around for another 5 mins to locate, to wait another 5 mins again to relocate the last time, as, having fixed it's location 5s previously, didn't know where to look for itself.
On the run was generally ok apart from the usual unbelievable HR, but also unbelievable pace as well today. Pause and restart fixed that. Generally the track was poor with a couple of major wobbles and offsets - albeit not so obvious if you don't know where I went. Lots of twists and turns at speed will confuse it though, and tbh with the delays in locating I was expecting the run to be offset by literally miles.
End of the run was a bit of a nightmare as trying to upload the run would tell me "sync failed" without even properly trying, then the bluetooth turned off, and basically there was nothing that I could do to turn it back on short of waiting for it to do it itself, which it did after 20 minutes.
As of 9.30, I can sync with phone problem free - but desktop sync isn't as apparently there are "some temporary server issues" or "maintenance" (depending on how many times you click - their web status page says everything is fine and working). A bit annoying as I think it needs the desktop sync to fix all the things that have gone wrong from last night.
These are the sorts of bugs I 'd come to be used to with Finnish watches (I've never been impressed with the Garmins, but generally their platforms were robust). I do hope they sort whatever's wrong at their end, and fix the firmware a bit quicker than the long duration issues back in 2016/2017.
https://www.strava.com/activities/4045100121(One thing I will credit Polar with is that they keep a public log of server issues. I suspect yesterday's issue hasn't actually been resolved...)