Direct answer
For the Google Pixel Watch 2, auto-detection, profile settings, sensor fit, GPS lock and sync should be separated. First, start a manual controlled workout and note sensor/GPS indicators.
What this covers
- Google Pixel Watch 2 (G4TSL/GC3G8)
- Google Pixel Watch; Wear OS version, LTE versus Wi-Fi model, watch-face complications and paired-phone account state vary.
- The specific fault this record addresses: workout or activity was not recorded correctly
What it does not cover
- ×The same symptom on a different Google product line, which has its own record and its own cited source
- ×An on-screen error code whose meaning has not been checked against this exact model's manual
- ×Live electrical, gas, sealed-system, internal battery-cell or structural repair — a technician boundary, not a self-service step
Differential
What actually causes this, and how to tell them apart
These are ordered by how often each one is the answer, not by how easy it is to try. The point of the middle column is that two causes producing the same headline symptom rarely produce the same detail — that detail is what tells you which one you have before you change anything.
- 1
Auto-detection did not start or stop the workout as expected
What separates it A workout was partly captured, split, or not recorded, and it relied on automatic detection.
How to confirm Start workouts manually for activities that matter; auto-detection can miss the beginning, merge sessions, or not trigger for some activity types.
- 2
The wrong activity profile or settings were used
What separates it The metrics are wrong for the activity (a bike ride logged as a walk, no pool length set for a swim).
How to confirm Select the correct activity profile and its settings before starting; the profile controls which sensors and calculations are used.
- 3
Sensor fit or GPS lock corrupted the data
What separates it The workout recorded but the distance, pace or heart rate is clearly wrong.
How to confirm Cross-check the heart-rate and GPS symptoms; a loose watch or a workout begun without a GPS lock produces bad but present data.
- 4
The workout captured but did not sync
What separates it It shows on the watch's own history but not in the phone app or online.
How to confirm Force a sync and check the not-syncing causes; the data is safe on the watch until it transfers, so do not reset before it does.
Before you touch a setting
Record this first — changing settings destroys the evidence
Every item below stops existing the moment a reset, re-pair or settings change is made. Written down first, they are what separates the causes above; recovered afterwards, they are guesswork.
- Whether the workout appears in the watch's own history but not the app (a sync issue).
- Whether it relied on auto-detection or was started manually.
- Whether the correct activity profile and its settings were selected.
Start a manual controlled workout and watch the sensor/GPS indicators
ReversibleRemoves auto-detection and confirms capture in real time.
Compare the watch's own history against the app to place the fault
ReversibleOn the watch but not the app is a sync problem; missing on both is a capture problem.
Correct the profile, detection or sensor fit, or recover via sync
ReversibleFix capture and sync separately, whichever the comparison showed.
Complete and sync another controlled workout to confirm
ReversibleVerifies both capture and transfer end to end.
Model-specific
What is true of this model and not of its siblings
Generic advice for the product line fails here. Each item below is a property of this specific model family that changes which of the steps above apply to you.
- Model scope
- G4TSL/GC3G8. Google Pixel Watch; Wear OS version, LTE versus Wi-Fi model, watch-face complications and paired-phone account state vary.
- Model — Pixel Watch 2
- Google's Wear OS smartwatch with Fitbit health sensors (heart rate, skin temperature, cEDA stress), a speaker/mic for calls, in Wi-Fi or LTE versions. All wearable symptoms apply, cellular on the LTE model.
- Cellular is optional (a variant)
- Wi-Fi or LTE — cellular applies only to the LTE model with a carrier plan. A Wi-Fi model relies on the phone/Wi-Fi.
- Pairs with Android
- Wear OS pairs with Android only; health data via the Fitbit app. Pairing issues are often the Android/Fitbit/Google-account step.
- Backup path
- Carries a cellular backup path for alarm signalling. Backup carries signalling, not bandwidth — so the system can report itself online and monitored while everything that needs broadband fails, and can stay in that state for weeks unnoticed.
- Symptom boundary
- This record covers Google Pixel Watch 2 when it workout or activity was not recorded correctly. A different symptom on the same hardware, or this symptom on a different Google product line, has its own record with its own causes and its own cited source.
Stop boundary
When this stops being a self-service repair
Continuing past any one of these costs more than the repair saves — in safety, in warranty, or in evidence a technician needs.
- !Do not edit or delete health records blindly to 'fix' a workout — preserve the originals before any edit, and do not reset the watch while a captured workout is still unsynced.
Evidence ledger
Sources behind this answer
Visible sources support the visible claims. Home Product Support records the publisher, the fact used and the review date; community reports can suggest an issue but do not become a published fact on their own.
Where the manufacturer's article stops. Google Pixel Watch Help publishes this as "Google Pixel Watch Help". Official Pixel Watch setup, charging, sync, health-sensor and Wear OS support. What that article does not carry is the model boundary — it is written for a product line, and G4TSL/GC3G8 is the scope applied here. Where a control label, terminal, indicator pattern or reset sequence differs on your unit, the manual for that exact model is the authority, not this page and not the article.
Exact questions
Common follow-ups
My Pixel Watch 2 won't pair with my phone.+
First confirm your phone is Android — Wear OS (and the Pixel Watch) does not pair with an iPhone. Then update the phone, the Pixel Watch and Fitbit apps, sign in to the same Google account, keep both devices charged and close together with Bluetooth on, and follow the in-app pairing. If it was paired to another phone, factory-resetting it may be required, but understand that erases it — so resolve the account/app steps first. Most pairing failures are the account or an out-of-date app.
My workout didn't show up in the app.+
First check the watch's own activity history. If the workout is there but not in the app, it is a sync problem — force a sync and it will transfer, so do not reset anything, because the data is safe on the watch until it does. If it is missing from the watch too, it was not captured: relying on automatic detection is the usual reason, since it can miss the start or not trigger at all, so start important workouts manually and pick the correct activity profile first.
Does this answer apply to every Google model?+
No. It is scoped to G4TSL/GC3G8. Google Pixel Watch; Wear OS version, LTE versus Wi-Fi model, watch-face complications and paired-phone account state vary.
What should I record before troubleshooting workout missing or activity?+
Record the complete model identifier, exact message or indicator, software/firmware where visible, the operating stage and what still works.
Why is a factory reset not the first step?+
A reset can erase accounts, networks, maps, schedules or preferences without distinguishing workout missing, activity. The ordered checks preserve that evidence.
When should I stop and use qualified service?+
Do not alter health records blindly; preserve originals before edits.
Answer for the exact device and software version shown above.