Apple Watch Complications Not Updating? How to Fix It
A complication that looks stuck is usually working normally. Complications refresh on a schedule, not continuously, so a few minutes of lag is expected. When the lag is hours, three settings explain nearly every case: Background App Refresh switched off, Low Power Mode switched on, or the app not being installed on the watch itself. Check those in that order, then remove and re-add the complication before restarting anything.
Why complications are never truly live
The expectation is the problem more often than the watch is. A complication looks like a live readout, so people assume it behaves like one — but almost none of them do. What sits on your dial is the last value the app handed over, redrawn each time the screen wakes. Between hand-overs the number simply sits there, correct as of whenever it was collected.
watchOS works this way deliberately. Letting every app on the watch fetch data whenever it liked would flatten the battery by mid-afternoon, so the system schedules background updates and gives the largest share of that budget to the face you are currently wearing. Some complications are exempt in practice because they need no fetching at all — the date, a timer counting down, the battery percentage. Everything that depends on a sensor, a server or your iPhone is on the schedule.
Two consequences follow, and together they cover most of what people report as a bug. A number that is a few minutes old is not a fault. And a complication that is hours old has almost certainly had its background access removed by a setting rather than broken on its own.
Work through it by symptom
Start with what you can actually see on the dial. The symptom narrows the cause faster than working down a generic checklist does, because a blank slot and a stale number fail for completely different reasons.
| What you see | Likely cause | What to do |
|---|---|---|
| The number is right but a few minutes old | Normal scheduling — complications refresh in batches, not live | Nothing to fix. Tap the complication to open the app for a current figure |
| A dash, a placeholder or a greyed-out icon | The app has no data yet, or is not installed on the watch itself | Open the app on the watch once, then check the face again |
| Frozen since this morning, across several apps | Background App Refresh off, or Low Power Mode on | Check both in the Watch app and in Settings on the watch |
| Weather shows the wrong place or no temperature | Location permission or no connection when it last tried | Re-check Location Services for Weather on the iPhone |
| Data hidden until you raise your wrist | Always On is redacting sensitive complications by design | A display setting, not a fault — turn it off if you prefer |
| Only one particular app is stuck | That app’s own refresh, not watchOS | Remove and re-add the complication, then update the app |
The distinction that matters most in that table is one app versus all of them. If a single complication is stuck while the rest are current, the cause is inside that app. If everything froze at the same moment, the cause is a system setting and you can stop investigating individual apps entirely.
The five-minute sequence
Run these in order. They are arranged cheapest-first, and the great majority of cases are resolved before step four.
- Raise your wrist and wait a moment. The dimmed Always On state redacts some values and refreshes more slowly. Judge the complication with the screen fully awake.
- Check for Low Power Mode. A yellow indicator at the top of the face means background refresh has been cut back deliberately. Charge the watch or switch it off in Settings.
- Check Background App Refresh. On your iPhone, open the Watch app → General → Background App Refresh. Confirm the master switch is on, then find the specific app in the list beneath it.
- Open the app on the watch once. This forces a fresh fetch and confirms the watch half of the app is installed at all — the commonest cause of a permanent placeholder.
- Remove and re-add the complication. Press and hold the face, tap Edit, swipe to Complications, set the slot to Off, save, then add it back. This discards whatever stale value watchOS was holding.
- Restart the watch. Only now, and only if several apps are affected. Hold the side button, power off, then hold it again to restart.
- Update watchOS and the app. A complication broken by a specific version is a developer fix, not a settings fix — there is nothing on the watch left to try.
Notice what is not on that list: unpairing and re-pairing your watch. It costs the best part of an hour, and no complication problem has ever needed it. If a change you made on the iPhone is not reaching the wrist at all, that is a syncing problem instead — the syncing troubleshooter is the right page for it.
When the data is fine and the slot is the problem
A distinct failure worth separating out: sometimes the complication is not stale, it is missing. A face you edited months ago can come back with a slot set to Off, usually because the app behind it was deleted and watchOS quietly cleared the slot rather than leaving a dead shortcut on your dial.
The same is true of a complication that will not appear in the list to begin with — an app supplies each slot shape separately, so it can be offered in a corner and absent from a rectangular slot on the same face. That, plus the full add-and-edit route on both devices, is covered in how to add complications to your Apple Watch face. Step count is its own case, because Apple provides no Steps complication at all — showing steps on your face explains what to use instead.
A dial you read, not one you debug
Once you have it working, the useful lesson from all of this is about restraint. Every complication you add is one more thing that can look stale, and most people genuinely read two of them. A face carrying six is slower to scan and gives you six chances to notice a number that is twenty minutes old.
The pattern that holds up is a small working rotation: one dense face for the hours when you need data, one clean face for everything else. The Watch Lux gallery holds 500+ AI-crafted faces across live/animated, 3D depth and photo styles — the minimal designs sit well alongside a slot or two, and the dark & OLED designs keep small complication text high-contrast on the Always On display. A new themed collection lands every week, and legibility comes down to contrast and clutter far more than to which face you picked.
Why is my Apple Watch weather complication not updating?
Weather is fetched, not calculated on the wrist, so it fails in two places. Either the watch had no connection the last time it tried, or Location Services is switched off for the Weather app on your iPhone. Check the permission first, then open the Weather app on the watch once to force a fresh pull. A complication showing the wrong city is nearly always a location problem rather than a broken face.
Weather is the complication people notice first, because it is the one they check without thinking. It is also the most dependent on things outside the watch. If your watch spends the day away from its iPhone and off Wi-Fi, and it is not a cellular model, the temperature on your dial is the last one it managed to download — which can easily be hours old by lunchtime.
Worth knowing before you go hunting through settings: weather also lives in the Smart Stack, one turn of the Digital Crown from the face. If the widget there is current and the complication is not, the fetch is working and the complication simply has not had its turn yet.
Why does a third-party complication show a dash or a placeholder?
A placeholder means watchOS has drawn the slot but the app has given it nothing to show. The usual cause is that the app is installed on the iPhone but not on the Apple Watch, so nothing on the wrist is producing data. Opening the app once on the watch normally fills it in. If it stays empty after that, the app has not been granted the permission it needs.
The install point catches people out constantly, because an app can appear in the complications list on the iPhone while the watch half of it was never installed. Open the Watch app on your iPhone, find the app in the list, and confirm it is switched on for the watch.
Permissions are the second half. A sleep, fitness or heart app that has not been allowed to read Health data will render a perfectly valid, permanently empty complication. Nothing about the face is wrong; the app simply has no numbers to hand it.
Does Background App Refresh affect watch face complications?
Yes, directly. Background App Refresh is what lets an app wake up and hand fresh data to its complication between the times you open it. With it switched off — globally or for one app — the complication only updates when you open the app yourself, which looks exactly like a frozen complication. You will find the setting in the Watch app on your iPhone under General, with a per-app list beneath the master switch.
This is the single highest-yield thing to check when several complications have gone stale at once, because one toggle explains all of them. People switch it off during a battery-saving phase, forget, and then spend weeks assuming watchOS is buggy.
The per-app list underneath matters as much as the master switch. Leaving it on globally but off for the two apps you actually read produces the most confusing version of this problem — some complications current, others stuck, no obvious pattern.
Does Low Power Mode stop complications from updating?
It restricts them. Low Power Mode exists to cut the background work your watch does, and background refresh is precisely that work — so complications update far less often, or wait until you open the app. Some sensor-driven readings are reduced as well. If your complications went stale on the same day your battery ran low, check for the yellow indicator at the top of the face before changing anything else.
The tell is that everything goes quiet together rather than one app misbehaving. Low Power Mode can also switch itself on automatically at a low charge and stay on until the watch is charged, so it is easy to be in it without having chosen it.
If you spend a lot of time in Low Power Mode by choice, treat the dial differently: keep the complications that are still useful when slightly old — date, battery, a shortcut you tap — and stop expecting live figures from it. What actually drains an Apple Watch covers where the power really goes, and the answer is rarely the face.
Why do complications go blank when my wrist is down?
That is Always On working as designed, not a failure. When the display dims, watchOS can redact complications it considers sensitive — activity figures, heart data, calendar entries — so the person opposite you cannot read them off your wrist. Raise your wrist and the values come straight back. It is a setting rather than a rule: the option to stop hiding them sits in the Watch app under Display & Brightness.
It reads as a bug because the timing looks like a data failure — the number vanishes and reappears. Once you know it is a privacy behaviour, the choice is a genuine one. Hidden data is the safer default in an office or on a train; visible data is better if you glance at your wrist mid-task without lifting it.
A second, subtler effect: the dimmed Always On state is drawn at a lower refresh rate, so a number can be a minute or two behind the moment you look at it. Raising the wrist resolves that too.
Does removing and re-adding a complication force it to refresh?
Often, yes — and it is the right thing to try before anything drastic. Press and hold the face, tap Edit, swipe to Complications, set the slot to Off, save, then add the complication back. That makes watchOS discard what it was holding for that slot and ask the app for it again. It fixes a single stuck complication far more often than restarting the watch does.
Do it in that order, though. Re-adding is cheap, targeted, and takes twenty seconds; restarting the watch is the blunter instrument and only helps when several things have gone wrong at once. Unpairing and re-pairing is not a step in this problem at all — no complication issue justifies it.
If you have forgotten the editing route, the complications guide walks it on both the watch and the iPhone, including the slot shapes that decide which apps you are even offered.
Why does a complication update on one face but not another?
Because watchOS spends its refresh budget on the face you are actually wearing. A complication on a face sitting further along your list is not being kept current in the background at the same rate, so it can look badly out of date the moment you swipe to it — then correct itself shortly after. Give it a minute on screen before deciding that face is broken.
This one is worth internalising if you keep a large rotation, because the symptom is entirely predictable: the face you swipe to twice a week always looks stale for the first few moments. That is the system prioritising sensibly, not a fault in the face.
It is also an argument for a small working rotation and a large wardrobe — how many faces you can keep makes the case for curating the list rather than hoarding it.
Do complications on a photo or custom face update differently?
No. A photo-style face has fewer slots than a data-dense dial, but whatever slots it does have behave exactly like the ones on an Apple face — same refresh scheduling, same Background App Refresh dependency, same permissions. Nothing about the artwork changes how the data arrives. If a complication is stale on a custom face, it is stale for one of the ordinary reasons on this page.
Custom designs installed from an app reach your wrist as photo-style faces, because Apple does not allow fully native third-party watch faces. That affects how many complications you can place, not whether they work. Apple documents the editing surface itself in its customize the watch face guide.
If the face itself never arrived — as opposed to its data being old — that is a different problem with a different fix: the syncing troubleshooter covers a face that will not land on the watch, and the switching troubleshooter covers one that will not change.
Keep one face for data, one for the rest
Complications earn their place on a working face. For the other twelve hours, Watch Lux is free to download, installs a design in one tap, and adds a new collection every week.
Get 500+ Faces FreeFree to download · Pro unlocks the full catalog (pricing shown in the App Store) · iPhone iOS 16.2+ and Apple Watch watchOS 10+