Why is the heart rate on my Garmin watch face old or not updating?
A watch face shows the heart rate the watch reports at that moment, and when there is none, some faces fall back to the last valid reading from the past minutes. With that fallback in use, the number on the face can be several minutes old.
Current value or last valid reading
A face has two sources, and which one it uses decides how old the number can be. The current heart rate is a value in beats per minute or nothing (Activity.Info, checked 9 November 2026). The heart rate history holds earlier samples, each with its time, and marks unusable ones as invalid (ActivityMonitor). Umbra reads the current value first. If there is none, it takes the newest valid sample from the last 540 seconds, refreshed once a minute, so the number is at most ten minutes old; otherwise it shows --. This fallback is built and described here as a mechanism; it is not yet confirmed on a real watch, because the simulator cannot control heart rate.
What happens when the watch wakes up
The face reads its cached values again right away. Values such as the heart rate history, stress and Body Battery sit in a cache that refreshes once a minute. Since Umbra 1.2.1 that cache is reset when the watch wakes up, so heart rate, stress and Body Battery refresh immediately instead of up to a minute later.
What Bluetooth and sync have to do with it
Nothing. Both sources are on the watch: the current value from the wrist sensor and the history the watch keeps itself, which a face can read without any extra permission. A disconnected phone or a pending sync with Garmin Connect does not make the heart rate on the face older. Sync matters for values such as weekly distance, see why a watch face shows --.