Low Heart Rate Event

A Low Heart Rate Event records a low-rate notification from Apple Watch. It is not the same thing as every low Heart Rate sample. The category value 0 (notApplicable) identifies the event; the configured beats-per-minute threshold appears in separate metadata. Apple's HealthKit documentation describes these samples as read-only.

Apple Watch can notify you when your rate remains below the chosen threshold after at least ten minutes of apparent inactivity. See Apple's heart-health guide. This setting is not a personalized medical assessment. A rate below a clinical definition of bradycardia does not guarantee a watch notification, and a saved event does not establish a conduction disorder.

Low rates can occur during sleep or in physically trained people. Their significance depends on symptoms, baseline, medications and other clinical context. The American Heart Association's bradycardia guidance discusses these differences. Sleep overlap alone cannot certify that an event is harmless.

The October 2025–September 2026 window contained three events on three dates, all from the same source revision. All used category code 0 and stored a 40 bpm threshold. Each stored interval was exactly ten minutes. No events appeared in the July–September focus window.

Nearby samples here start within five minutes before the event start through five minutes after its end. They are a temporal comparison across exported heart-rate sources, not an explicit HealthKit association. The ten-minute record is not evidence that every instant stayed below 40 bpm. Three notifications do not support stable percentiles, a typical event rate or a disease-risk estimate.

All three event intervals overlapped a recorded asleep interval; none overlapped a recorded workout. That is a description of these examples, not a rule that low notifications only happen during sleep. The stored intervals and nearby readings cannot identify the cause of a low rate.

The long gaps between saved events describe notification timing. They do not show continuous monitoring, uninterrupted normal readings or time without bradycardia. Notification settings and watch-wear opportunities on days without an event were unavailable.

Use raw heart rate to examine the surrounding readings and Resting Heart Rate to follow a different daily summary. Sleep Analysis supplies recorded context. An available ECG may capture electrical rhythm, but a recording at another time cannot explain the event retrospectively.

The database had no AFib-burden records and no VO2-max estimates in these event comparison windows. That does not exclude AFib or establish fitness as the explanation. An irregular-rhythm notification or a high-rate event nearby also does not independently diagnose a rhythm syndrome.

Discuss new, recurring or symptomatic episodes with a clinician. A sudden unusually slow pulse accompanied by chest pain, breathlessness, dizziness or fainting needs urgent assessment; see the AHA heart-rate guidance. Do not change medication or dismiss symptoms based on a sleep label, fitness score or watch threshold alone.