[BUG] - Glance widget data different from details page

Recently I’m seeing that the glance widgets and the detail pages for them aren’t matching. For example, yesterday my load focus widget shows 0 high aerobic, but when I clicked on the glance widgets, it would show the high aerobic workout I did from 2 days ago. It took 2 days for the widget to finally update and show the stuff below. Similarly, training readiness almost never matches what is shown when I actually click on the glance widget. Even if I try to pull down to refresh the detailed page, it doesn’t update even 5ish hours later (see second image).

  • I'm linking a support article to review regarding this here: Missing Data From the Home Page in the Garmin Connect App

    If you haven't already tried I'd also sync your device with Garmin Express, ensure your Garmin Connect app is up to date and sync the device again by tapping the circular arrows in the top right of the screen again. 

  • I've already tried updating the app and syncing the device. The main issue seems to be a lack of consistency in how already synced data is being displayed in the app. Different pages show different values. Looks like the Garmin app isn't using a single source of truth for the data being displayed in the glance widgets and on the detail pages and so this bug needs to be fixed.

  • I’m having a strange syncing/data consistency issue with Garmin Connect on iOS while using my CIRQA.

    The data shown on the Garmin Connect homepage does not match the data shown when I open the individual metric.

    For example, the Sleep card on the homepage might show a score of 60, but when I tap it and open the full Sleep page, it shows 58.

    The same thing happens with other metrics. A metric might show 95 on the homepage, but when I open the detailed page, it shows 93.

    Refreshing and syncing the app does not seem to fix it. This makes it difficult to know which number is actually accurate.

    Is anyone else experiencing this with CIRQA and Garmin Connect on iOS? Is this a known syncing or caching bug?