Symptoms
- The dashboard shows an expired-grant or reconnect prompt.
- Email, calendar, or Slack context stops updating.
- Notetaker dispatch, drafts, scheduled runs, or Slack delivery looks stale.
- A reconnect succeeds, but data still appears to come from the wrong account or workspace.
Most common causes
- OAuth grants can expire, be revoked, or be invalidated by account/security policy changes.
- The user reconnected with a different account than the one that owns the mailbox, calendar, or Slack workspace.
- Slack channel membership, workspace, or channel mappings changed after reconnect.
- Required scopes or channel access were not granted during the new connection.
What to check
- Use the reconnect prompt when the expired-grant blocker appears.
- Reconnect with the same work account expected to own the source.
- Confirm Google or Microsoft email/calendar permissions were granted during the OAuth flow.
- Confirm Slack workspace, channel membership, and private/external channel access where Slack is the affected source.
- Retry one affected workflow after reconnect before assuming all historical data is repaired.
Resolution steps
- Reconnect only the affected source first.
- If Slack still cannot find a channel, add Ergo to the channel or confirm the connecting user can see it.
- If calendar or email still looks stale, confirm the connected account matches the user’s active mailbox and calendar.
- Do not assume reconnect backfills missed meetings, messages, or draft context automatically.
When to contact support
- Contact support when the correct account is reconnected, permissions are granted, and one controlled workflow still fails.
- Include the workspace, affected user, source system, connected account, workflow tested, and approximate time window.
- Keep examples generalized and avoid sharing sensitive customer content in support requests.