The problems runners actually hit โ each with the reason and the fix. Most take under a minute.
Why it happens: FLUX reads heart rate through Apple Health, and the read permissions were declined or switched off. Apple doesn't let apps ask twice — so it has to be fixed in Settings.

Why it happens: an Apple limitation — the watch only measures heart rate continuously while a workout is running on the watch itself. Without one, it samples every few minutes.

Want zero-lag heart rate? A Bluetooth chest strap streams directly to FLUX in about a second — the fastest option there is.
Why it happens: most sensors only broadcast when they're on your body — and Garmin watches only broadcast after you turn it on, on the watch itself.



Why it happens: the sneakiest one on this list. When you start an activity on the Garmin (to record the run there too), the watch stops the regular broadcast — unless a separate setting says otherwise.



Only recording your runs in FLUX? Then you don't need this — the regular broadcast keeps going as long as you don't start an activity on the watch.
Why it happens: Fitbit, Samsung and Xiaomi watches don't broadcast heart rate in the standard Bluetooth format, and don't write to Apple Health in real time. There's no way for any iPhone app to read them live.

Why it happens: one of two things — there's no active Apple Music subscription (FLUX plays through your Apple Music account, so it's required), or your library is still being tagged and the zones are empty.

That's not a bug — that's the engine being smart. FLUX waits until your heart rate holds steady in the new zone for 30 straight seconds before switching tracks. Without it, every hill and traffic light would cut your music mid-beat.
Why it happens: FLUX doesn't have location permission — or has it without Precise Location, which GPS tracking needs.

Email us what's happening — a real person reads it and answers.