Troubleshoot an integration
The most common issues and how to fix them.
The vast majority of integration issues come down to 3 causes: expired tokens, insufficient scopes, or provider-side rate limits. This guide covers symptoms and associated fixes.
Integration disconnected
Symptom: red `Disconnected` badge on the integration, Nexte notification. Common cause: expired OAuth token (password change at provider, manual revocation, app update).
- Settings → Apps → find the affected integration.
- Click `Reconnect`. You're redirected to the provider's OAuth screen.
- Approve permissions. Auto-return to Nexte with integration shown in green.
- Previously synced data stays intact, sync resumes immediately.
Data not showing up
Symptom: integration is green but nothing happens, new entries on the provider side absent in Nexte. Possible causes: sync delay (up to 5 min normally), insufficient OAuth scope, restricted permissions on the provider side.
- Check status: Settings → Apps → `i` icon next to the integration. Shows last successful sync, last error, synced items count.
- Force resync: `Refresh` button in the integration. Useful if an automatic sync silently failed.
- Check scopes: reconnect the integration to refresh permissions (useful if new scopes were added by a Nexte update).
- Check provider side: does the data actually exist? A read-marked email, an archived Notion page, a Figma file in an unauthorized space aren't synced.
429 error / rate limit
Symptom: `Too many requests` notification or lagging integration. Cause: the provider caps API calls per hour or day. Nexte auto-applies exponential back-off (1s, 2s, 4s, 8s, 16s, 32s) and retries each request until success.
- Typical duration: auto-resolution within 5-15 minutes.
- If lasts > 1h: probably a Google/Microsoft/HubSpot quota issue on your account. Check your provider dashboard.
- Workaround: disable real-time sync and switch to `Hourly` mode to reduce load.
- Support: if lasts > 4h, contact Nexte support with the error log (available in the integration screen).
Bidirectional sync conflict
Mostly applicable to CRMs (HubSpot, Pipedrive) when the same entity is edited simultaneously on both sides. Nexte applies a `last-write-wins` rule: the most recent change wins. The other is archived in an audit log kept for 30 days.
Integration that keeps disconnecting
Rare but possible. Known causes: 2FA enabled without app-password on Google Workspace, enterprise security policy auto-revoking OAuth tokens, antivirus intercepting OAuth callbacks.
- Google Workspace: ask your IT admin to whitelist the Nexte OAuth app in Marketplace settings.
- Microsoft 365: same on Entra ID. Admin consent may be required.
- 2FA: always use OAuth (not a password) — the 2FA flow is transparent to Nexte.