> For the complete documentation index, see [llms.txt](https://docs.tryterra.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tryterra.co/faq/help-topics/no-data/delivery-delays-lag/google-health-connect-data-delay-reinit.md).

# Why are my Google activities arriving with a delay?

There are two cases, depending on how Google is connected.

**Google web connections** are polled on Terra's schedule, and the API only returns what the device has already synced to Google's cloud. A new connection's first data can therefore lag until the first poll cycle, plus Google's own sync timing.

**Google Fit / Health Connect via the mobile SDK** only flows data when your app calls `initConnection`. There is no background poller while the app is closed.

To keep data fresh, **call `initConnection` whenever the app returns to the foreground**. An 8-hour per-data-type cooldown prevents excess churn. See the [mobile SDK docs](https://docs.tryterra.co/health-and-fitness-api/mobile-only-sources) for the call pattern.