Reconnect a disconnected sender
Steps to bring a disconnected sender back online, from checking delegation and scopes to re-authenticating all senders at once.
Open in Tantra
These open the app in a new tab. You may be asked to sign in.
Overview
A sender becomes Disconnected when no uploaded service account can impersonate it. This usually means delegation was changed or removed, a scope is missing, or the service account was deleted. This article walks through bringing it back online.
Before you start
- Admin access to your Google Admin console to check delegation and scopes.
- Your service account uploaded to Tantra. See Upload your service account to Tantra.
Step-by-step
- In the left sidebar, click Accounts, then set the status filter to Disconnected to see affected senders.
- In your Google Admin console, confirm that domain-wide delegation still lists your service account's client ID with the correct scopes. See Grant domain-wide delegation and scopes.
- Back in Tantra, click Re-authenticate All to re-check every sender against your service accounts.
- If only one sender was affected, you can instead re-paste its address in Verify and Add Accounts and click Verify & Add.
- Confirm the sender now shows Connected.
What happens next
Re-authenticating re-runs the impersonation check for your senders. Any sender whose delegation and scopes are correct returns to Connected. If it stays disconnected, the problem is on the Google side, usually a missing scope or the wrong client ID.
Notifications
Tantra emails you once a day when senders are found disconnected, so you learn about dropped connections without watching the page. Use that email as a prompt to re-check delegation and re-authenticate.
Common mistakes
- Re-authenticating before fixing the Google side. If delegation is still wrong, the sender stays disconnected.
- Deleting and re-adding a sender instead of fixing delegation. Re-authenticating is enough once Google is correct.
Troubleshooting
| Symptom | Cause | Fix |
|---|---|---|
| Still disconnected after re-authenticating | Delegation missing, wrong client ID, or scopes removed | Fix the delegation entry in Google, then re-authenticate |
| Reconnects for calendar but not Gmail | Gmail scopes not granted | Add gmail.send and gmail.modify, then re-authenticate |
| The service account was deleted | Its key was removed from Tantra or Google | Re-upload a valid service account and verify again |
FAQ
What is the fastest way to reconnect everything?
Fix the delegation in Google if needed, then click Re-authenticate All on the Accounts page.
Why did my sender disconnect on its own?
Something changed on the Google side: delegation was edited, a scope was removed, or the service account was deleted or disabled.
Will Tantra tell me when a sender drops?
Yes. Tantra sends a daily email listing disconnected senders.
Do I lose my sender settings when I reconnect?
No. Reconnecting refreshes the impersonation check. Your per-sender settings remain.
Related articles
Was this article helpful?
Related articles
- Sender connection states explainedUnderstand the Connected, Disconnected, Gmail capable, and Calendar-only states Tantra shows for each sender mailbox.
- Add and verify your sendersPaste the mailboxes you want to send from and verify them against your uploaded service accounts using domain-wide delegation.
- A sender shows as disconnectedFix a sender that shows as disconnected. Check domain-wide delegation, Gmail and Calendar scopes, and re-verify the mailbox against your service account.