Data quality
- 
@Dimitrios-Kanellopoulos
 my deepest apologies⊠the answer NOW (and obviously since the last update) is NO, NO LONGER ANY DIFFERENCES.
I keep a (kind of) training diary in my calendar, and got stuck with older entries. So once more apologies for the unnecessary and not fact-based fuss I created with the second part of my last post.
 - 
@Shrek3k its OK man. Even if it was so, believe me , I want this data quality issue to be closed.
 - 
At a first glance, it seems that 3.45.1 fixed the OHR issue, as expected
 - 
@Dimitrios-Kanellopoulos
Unfortunately, at a second glance
, Iâve seen that the moves done with 3.45.0 are now wrong. The issue is similar : watch Z1 is shown as Z2 in app and the graph is messed up. Iâll attach some images soon
Iâll try to unpair/full resync this evening
 - 
@sartoric confirmation of this issue; by the way - the older activities have been âpushed upâ, too, and are looking correct now.
Looking forward to new activities and to see how they are handled. - 
@sartoric mine are not
 - 
@Dimitrios-Kanellopoulos
Because youâre lucky
 you didnât have the old issue too, isnât it ? - 
Suunto 9 and latest beta app and same issueâŠ
 - 
@sartoric I had the old issue for sure.
 - 
Hi can I have links of the moves that now have wrong zones ?
 - 
@Dimitrios-Kanellopoulos
Oh, I misunderstood. - 
@Dimitrios-Kanellopoulos said in Data quality:
Hi can I have links of the moves that now have wrong zones ?
 - 
@sartoric suunto app links please
 - 
@Dimitrios-Kanellopoulos
Ok. Iâm not yet familiar with all this devilry
https://www.sports-tracker.com/workout/cristian800101/5b9d49a6b99d9621ed0f8ff2
 - 
@sartoric I see in your photo also some translations wrong ? What language is this ?
 - 
@Dimitrios-Kanellopoulos
Italian. But it looks more as overlapping numbers - 
Unfortunately the buggy version 3.45.0 will habe those zone issues.
I am sorry but this cannot be undone (aka the 3.45 messed it up)
I donât know what to say except sorry
 - 
Ok. So those few moves are messed up, but a resynchronization could fix it or OHR data are managed in a different way ?
I mean, just for the sake of knowledge, what if I could (but I canât) delete and sync the moves again ? - 
@sartoric that should fix it.
I have been testing 3.45.1 for a week now and did not see any issue
 - 
As expected, new moves look ok.