Time error in zones

You don't see how much time you spent below 122 bpm. Check your HR graph and you will likely see that you spent about 41% of the time below 122.

Very thank`s!

I checked more carefully, because yesterday I realized that I was walking at a calmer pace, but it was several hours and more than 50 km of MTB. And my wife's garmin registered everything differently, and much closer to the real one.
Could it be a mistake of my instinct? you can't go mtb for so many miles and be less than 122 bpm, but my watch had always worked fine, and there was no recent update.
Thank you

Could you post the HR graph fro the MTB ride so we can look at it?

Are you wearing a chest strap or using the optical wrist heart rate? Optical wrist HR will often give lower readings than the real HR.

Hi, thanks for the interest.
I don't have cardiac girdles, I just use the Instinct. I understand that it is less precise, but I have been using it since March 2021, and something similar has never happened to me. So I think something did not work on the watch, and I was wondering if it is something that has happened to other people.
I have version 16 of the firmware. I think I'll pass this popst to the Instinct team, because it's clearly not a Connect bug.

Looking at the graph, it seems clear to me that most of the time I was at more than 122 bpm ... that's why I don't understand the registration of the zones in the other graph ...

A quick estimate gives me about 25% under 122 bpm. It is hard to say exactly how it measures it since it needs several points to get a time range to put in each zone.

It is probably easier if you just make your zone 1 include all values from your resting HR. Then do another activity and check if the result is 100%.