Troubleshoot Gmail, Outlook and IMAP connections
Steps to diagnose authorization, provider permissions and missing email connections.
Mailbox connection troubleshooting
Gmail / Google Workspace
Symptoms: Consent denied, disconnected mailbox, or a scan failing to read eligible sent threads.
- Verify that you selected the Google account containing the sent conversations.
- Complete the Google authorization flow and approve required permissions.
- Check whether an administrator or Workspace policy prevents app authorization.
- Reconnect the affected mailbox inside Nudge and run a controlled scan.
If the same address exists in both Snoooz and Nudge, a legacy connection may need an explicit Nudge reconnect to grant the permissions required for scanning and draft creation.
Outlook / Microsoft 365
Symptoms: Microsoft tenant authorization errors, expired connection, or provider token errors.
- Confirm the correct Microsoft account and tenant.
- Ask your tenant administrator to review consent restrictions if the connection is blocked.
- Reconnect the Outlook mailbox in Nudge; verify the connection status.
- Retry a scan on that mailbox.
Important: A Microsoft provider-token issue is not necessarily an MCP OAuth problem. Test mailbox access in Nudge before changing your MCP client registration.
IMAP, Yahoo or iCloud
Confirm that the account supports the required IMAP connection, the hostname and port are correct, and any provider-specific app password is active. Provider support and plan availability can differ.
Wrong region or workspace
Global and EU accounts use separate environments. Ensure you are signed into the same region that owns the mailbox. An agency user may have access to only selected workspaces.
Still failing?
Collect your account region, provider, timestamp and exact error text. Contact support without sending credentials or mailbox contents.