magick Hello, I’m not sure whether I’m missing something, if this is the expected behavior, or if it’s a bug, but it seems that the heart rate zones are not saved at the activity level. As a result, whenever I update my zones at a given moment, all past activities are recalculated using these new zones, which distorts the historical data and the analysis. Have I misconfigured something, or is this a known/expected behavior in Runalyze? Thanks for your help. --- Bonjour, Je ne sais pas si je passe à côté de quelque chose ou s’il s’agit du fonctionnement normal (voire d’un bug), mais il semble que les zones de fréquence cardiaque ne soient pas enregistrées au niveau des activités. Conséquence : dès que je mets à jour mes zones à un instant T, toutes les activités passées se recalculent avec ces nouvelles zones, ce qui fausse l’historique et l’analyse. Ai-je mal configuré un paramètre, ou bien s’agit-il d’un comportement connu/attendu de Runalyze ? Merci pour votre éclairage.
mipapo Zones are for all time ranges currently and will be recalculated. Currently you cannot set multiple time ranges for a zone Feature requests for revisions https://ideas.runalyze.com/posts/55/zones-hr-power-pace-historicial-progress-zone-revisions
magick Thanks for your answer. In my opinion, it would make much more sense to store heart rate zone data directly inside each activity, the way Garmin does. This prevents historical data from being altered when zones evolve over time and keeps past analyses accurate and consistent. Having “frozen” zone data at the activity level would greatly improve the reliability of long-term training analysis.
mipapo magick As users might change the zones at some point we need to recalculate it. Vote for the revision feature to create time ranges where you can adjust the zones. Only activities within that time range will get recalculated when adjusted.