Cannot connect a device
Connecting sends you to the provider to approve access and brings you back to a callback page in VegaLoop. Most failures show up on that page.
What the callback page says
| Message | Meaning | What to do |
|---|---|---|
| Successfully Connected | Done. New workouts will sync automatically. | Nothing. The first import starts on its own. |
| Authorization Failed | You cancelled on the provider’s page, or refused every permission. | Select Connect again and approve the permissions VegaLoop asks for. Google Health refuses a connection where every data type was unticked. |
| Connection Failed | The provider approved but the hand-back to VegaLoop failed. | Try again in a few minutes. If it repeats, check the status page and then contact support with the provider and the time. |
| Set up Google Health first | Your Google account is not yet signed in to the Google Health app. | Sign in to the Google Health app on your phone with the Google account you want to connect, or migrate your Fitbit account to it, then connect again. |
| We couldn’t complete the connection. Please try connecting again. | A general failure during the connect step. | Try again. |
The card does not offer Connect
- Request access with Limited beta. Spaces are limited. The provider is in early access. Send the request; the support team adds people by hand and the card changes to Request sent. Keep an eye on your email.
- Coming Soon means the connection is not open to anyone yet.
- Beta on its own is informational; Connect works.
Token Expired
The provider’s approval ran out and VegaLoop could not renew it. The panel reads Your connection has expired. Please reconnect to resume syncing. The card still shows Manage and Disconnect: select Disconnect, then Connect, and approve again. Garmin and Suunto also show a Reconnect button inside the Manage panel’s workout push notice. Nothing already synced is lost, and the sync resumes from where it stopped. Expect this about every 3 months with Garmin, which asks for re-approval on that schedule. The providers and what each sends are in Supported devices and platforms.
If the status changes to Token Expired and then back to Connected on its own, a later renewal succeeded; nothing to do.
Error
The last sync failed for a reason other than the token. Select Sync Now in the Manage panel. If the panel reads The provider is temporarily limiting requests. Please try again in a few minutes., wait before retrying; VegaLoop retries by itself on the next sync.
Oura: some data types stopped
If your Oura membership lapsed, or you did not grant a permission, Oura refuses that data type while the rest keeps syncing. You stay connected. Renew the membership or reconnect and grant the permission.
Withings: connected but nothing arrives
Withings accounts created after 12 October 2026 need a Withings+ membership to share data with third-party apps. Separately, if Withings could not register for automatic updates when you connected, Sync Now still works but nothing arrives on its own; disconnect and connect again to fix it.
The Integrations page says Unable to reach the server
The page shows the providers it knows about but cannot read your connections. Reload; if it persists, see A page will not load.
Still stuck
Contact support with the provider, what the callback page said, and the time you tried. Never include your provider password.