Reconnect a datasource
A datasource needs reauthorization when its Connection Status flips to Reauthorize — typically because a source-platform token expired, the source-side role changed, or an API key was rotated. Reconnecting restores the credentials so sync can continue.
When to reconnect
Section titled “When to reconnect”The Connection Status column in Settings → Integrations → Datasources is the signal. Don’t reconnect based on Data Sync Status alone — those two are independent (see Integrations overview for the model).
| Symptom | Action |
|---|---|
| Connection Status shows Reauthorize | Reconnect |
Data Sync Status shows Active but the last-sync timestamp is hours old | First check Data freshness — don’t reconnect unless Connection Status actually says Reauthorize |
Data Sync Status shows Inactive | The sync was paused (via Stop Data Sync or platform-side). Reconnecting isn’t the fix — re-enable sync from the datasource detail panel. |
| You rotated an API key on the source platform | Reconnect with the new key |
| The source-platform account owner changed | The previous OAuth grant may no longer be valid; reconnect |
Reconnection flow
Section titled “Reconnection flow”- Go to Settings → Integrations → Datasources and find the affected platform row.
- Click the row to open the detail panel.
- Click Reauthorize.
- Follow the same flow as the original connection — OAuth re-auth in the source platform’s window, or paste the new API key.
- Connection Status returns to Connected and Data Sync Status returns to
Active.
Stop Data Sync — pausing without disconnecting
Section titled “Stop Data Sync — pausing without disconnecting”The datasource detail panel has a Stop Data Sync action separate from delete. Use it when you want to keep the credentials in place but temporarily halt sync — for a maintenance window, a billing-driven pause, or while debugging a downstream mismatch. Data Sync Status flips to Inactive until re-enabled; Connection Status stays Connected.
After reconnecting
Section titled “After reconnecting”Sync resumes on the platform’s normal schedule. The next scheduled sync pulls any data missed during the disconnection window. Check the DATA panel (top header) for the updated timestamp.
If the integration drops to Reauthorize again shortly after reconnection, the underlying issue is on the source platform side — a permission, role, or token-policy change. See Datasource won’t connect.