When the daily sync hangs

Once a day (and when you ask), Coco syncs: it reads the latest mail and calendar and rebuilds your brief. If that seems to hang — the brief looks stale, or a "syncing" state lingers — here is what to check.

Give it a minute first

A sync reads a window of mail and runs it through the model to build your brief, so it is not instant. A heavier day, or the first sync after a quiet stretch, takes longer. If it has only been a moment, let it finish before treating it as stuck.

Check the last sync time

Look at when Coco last synced successfully. If that timestamp is recent, the system is fine and you are likely just looking at a normal gap between syncs — you can trigger a fresh one manually. If the timestamp is clearly stale, something interrupted it.

Trigger a manual sync

Ask Coco to refresh, or use the refresh action, to kick off a new sync by hand. This clears most transient hangs — a sync that stalled on a momentary network blip simply runs cleanly the second time.

Check the Google connection

If syncs keep failing, Coco may have lost access to your Google account — an expired sign-in or a revoked permission stops it from reading new mail. Signing in again restores it. If sign-in itself misbehaves, see common Google sign-in errors.

Very large mailboxes

An unusually large or busy mailbox can make a sync run long, especially the first deep read. This is slowness, not a true hang — let the first one complete and subsequent syncs are faster because Coco only looks at what is new.

If it is genuinely stuck

If the last sync is stale, a manual refresh does not help, and your Google connection is healthy, then something needs a closer look. Contact support with the rough time it stopped working and we will dig in. If the brief is empty rather than stale, start with when the brief comes back empty.