Troubleshooting sync issues

Last updated: October 7, 2026

Start here

When data stops showing up, work through these checks in order. Most problems are solved by the first two.

1. Check the provider's own app. COORDINATOR can only see data the provider has finished processing. If a run isn't on Strava yet, or last night's sleep isn't in the WHOOP app, it can't be in COORDINATOR either.
2. Check the integration's row. Go to Settings → Integrations and look for a warning on the row. A red Reconnect needed badge or the message Access expired means the connection is broken. See the Access was revoked or expired section later in this article.
3. Check what's arrived. For wearables, open the row's menu and select Recent activity to see what COORDINATOR has received. It's the fastest way to tell whether syncing is working.
4. Pull missing data. For wearables, open the row's menu and select Sync history. It pulls the last 30 days and skips anything already imported, so running it more than once is safe.

If none of that helps, find your situation in the following sections.

Access was revoked or expired

What you see: a red Reconnect needed badge on the row, or Access expired with a note to reconnect.

Why it happens: the provider stopped accepting COORDINATOR's access. This is almost always one of these:

• You removed COORDINATOR's access in the provider's own settings.
• You changed your password with the provider.
• The provider expired the access on its own schedule.
• You declined a permission COORDINATOR needs when you connected.

How to fix it:

1. Go to Settings → Integrations.
2. Open the menu on the row and select Reconnect.
3. Sign in on the provider's site and approve access again. Approve every permission you want COORDINATOR to use.
4. For wearables, select Sync history to backfill what you missed while the connection was down.

If Reconnect doesn't work, select Disconnect, then Connect again.

An API key stopped working

Some integrations connect with an API key instead of a sign-in page, such as Hevy, Amy Food Journal, and some MCP servers.

Why it happens: the key was deleted or regenerated on the provider's side, it expired, or your subscription with the provider lapsed and the provider turned off API access.

How to fix it:

1. Create a new key in the provider's own settings.
2. In COORDINATOR, go to Settings → Integrations.
3. Replace the key on the integration's row:
   • For an MCP server, open the row's menu and select Update key.
   • For Hevy or Amy, there's no Update key. Open the row's menu, select Disconnect, then select Connect and enter the new key.

Check that you copied the whole key with no extra spaces. Keys are case-sensitive.

The provider is limiting requests

What you see: data arrives late, or an error says there are too many requests and to wait a moment.

Why it happens: every provider limits how often an app can ask for data. If many requests happen in a short time, such as a large Sync history right after connecting several sources, the provider tells COORDINATOR to slow down. COORDINATOR waits and tries again on its own.

How to fix it: wait. Rate limits clear on their own, usually within minutes. Avoid running Sync history repeatedly while you wait, because each run counts against the same limit. If data is still missing after an hour, run Sync history once.

An MCP server needs you to sign in

What you see: the server's row says it needs you to sign in, or COORDINATOR says it couldn't use a tool.

How to fix it: open the row's menu and select Reconnect or Sign in. If tools are missing or changed, select Refresh tools. For more, see Connecting an MCP server.

A mission's watch stopped

What you see: on a mission's Watching card, a row shows Stopped and a reason.

Why it happens: usually, the integration the watch reads from has a broken connection.

How to fix it: fix the integration first, using the sections earlier in this article. Then, on the Watching card, open the row's menu and select Try again. See Meet your strategist.

Data is late, missing, or doubled

New data hasn't arrived yet

Most providers send data within a few minutes of processing it, but some batch their updates. Confirm the data is in the provider's app, wait a few minutes, then use Sync history.

Older data is missing

A connection only receives data from the moment you connect. Use Sync history to pull in older records. Each provider allows a different amount of history.

The same workout appears twice

This happens when two connected sources report the same workout, such as a watch that sends to both Strava and Suunto. COORDINATOR removes duplicates within one source, but can't safely assume two sources describe the same event. Connect the single most complete source if you'd rather avoid this.

A value looks wrong

COORDINATOR shows what the provider sends. Check the value in the provider's app first. If it's wrong there too, correct it there, then run Sync history. If it's right there and wrong in COORDINATOR, contact us.

Apple Health and Samsung Health

These sources send data from your phone, so the usual fixes don't apply. There's no Sync history or Reconnect. See COORDINATOR Go mobile app guide.

Integration-specific help

Each integration's article covers problems unique to that provider:

• Wearables: Strava, Oura, WHOOP, Withings, Suunto, Hevy, and Amy Food Journal
• Apps and files: Google Drive, Notion, and Dropbox
• Phone health data: Apple Health and Samsung Health
• Everything else: Connecting an MCP server and Connections and integrations

Contact support

Email [email protected] from the address on your COORDINATOR account. Include:

• Which integration, and what the row in Settings → Integrations shows.
• What you expected to see, and whether it appears in the provider's own app.
• When it last worked, if you know.

Never send us a password for any connected account. If you need to send an API key for debugging, replace it on the provider's side afterwards.