Why does my Garmin watch face show -- instead of data?
A watch face shows -- when the watch hands it no value for that field, so there is nothing to draw. It is not a fault in the face: a well-built face shows -- on purpose instead of an invented number or a crash.
-- means no value, 0 means the value is zero
-- and 0 are two different answers. In our face Umbra, -- stands for "no value": the watch returned nothing, the value type does not exist on this watch, or the face could not subscribe to it. 0 is a real value the watch delivered, for example a weekly cycling distance of zero. A face that turns a missing value into 0 tells you something false, which is why the two are kept apart.
Does your watch support the value at all?
If your watch does not provide a value, the face shows -- for it permanently. A careful face checks every value before reading it and falls back to -- when the value is missing. Which values a watch provides depends on the model and its Connect IQ API level. In a simulator test on the original Venu, which stays below Connect IQ API level 4.2.0, a test build of Umbra rendered time, date, battery, weather, Body Battery and stress in July 2026; only the weekly distance stayed at --, because that watch has no complications. The article on complications lists which values arrive at which API level.
Is the sync with Garmin Connect missing?
Values that depend on data the watch has to receive first stay at -- until that data is on the watch. Garmin documents weather as "the most recently cached weather conditions", or nothing (Weather API, checked 9 November 2026); with no cached weather, the field is empty. Weekly distances come through Garmin's complications and include activities synced from outside the watch, so a ride that has not synced yet is not in them. Since Umbra 1.2.1, distance fields recover on their own when data is missing at start: a failed subscription is retried at most once a minute.
Did a firmware update change something?
A face carries no values of its own; it reads each one from the watch firmware while it runs. If an update changes what the firmware provides, a face that checks every value shows -- where a value is now missing, instead of crashing. The face does not need an update of its own for that, and a value the firmware provides again appears again.
Why do VO2 max cycling or weather show --?
Both show -- while the watch has no value yet. Garmin describes VO2 max as "calculated based on historical data" (UserProfile.Profile, checked 9 November 2026), so without cycling history there is no cycling VO2 max to show. The value exists from Connect IQ API 3.3.0 and on all 48 watches Umbra supports; whether the firmware fills it can only be seen on a real watch, because the simulator has no cycling profile. Weather is either the last cached conditions or nothing, so a watch that has not received weather yet shows --.
If a field shows dashes right after you installed a face, the install and customize guide covers the first sync.