If Google Workspace mail used to appear in Cedros and has stopped, check the connection status before signing in again. A lost authorization, a failed sync, a hidden message, and mail that never reached Gmail need different fixes.
This guide applies to the Google Workspace inbox connection on self-managed Cedros sites. If the account has never been connected, use Connecting your Google Workspace account instead.
Identify what stopped working
Open Settings → Site → Mail. Expand Other mail providers and find Google Workspace. If the native mail setup flow is showing instead, look under Use Google Workspace instead.
Record the displayed account, connection status, most recent Synced time, and any error. The account shown here is the site's Google connection, not a personal connection for each teammate.
| What you see | Start here |
|---|---|
| Reconnect Required or an authorization error | Reauthorize the same intended account using the reconnection steps below. |
| Connected, but new mail is missing | Check Gmail, run Sync now, and clear inbox filters before reconnecting. |
| Connected, but read or archive changes stay in Cedros | Check the Gmail write-access message and follow the separate permission-upgrade steps. |
| Push sync is expired or has an error | Test Sync now first, then investigate push renewal. |
| Not Connected or Disconnected | Confirm why the connection is absent before connecting it again. Another administrator may have removed it intentionally. |
| A missing Google app configuration message | Ask the installation administrator to restore the site's configuration. A new Google sign-in cannot replace it. |
| The expected message is also missing in Gmail | Investigate delivery to Google before changing the Cedros connection. |
If Google still works, your team can use Gmail directly while the Cedros issue is investigated, subject to your normal access rules. Coordinate replies so two people do not answer the same conversation from different places.
Check a connected account before reconnecting
- Sign into the exact Google account shown in the Cedros panel. Confirm that a recent expected message is present in Gmail; check its recipient and folder.
- In the Cedros Google Workspace panel, select Sync now. Wait for the result, then read the sync timestamp and any error. Avoid repeatedly clicking while a sync is still running.
- Open Email → Inbox. Clear previous searches and filters. If a mailbox picker is present, choose the relevant mailbox or All visible mailboxes, as appropriate for your access.
- Switch from Needs attention to All mail, or select Show all mail if the inbox says you are caught up. Search for a distinctive subject using Search mail. Check the relevant folder if the message was archived or moved.
- If Gmail has the message but Cedros still does not, record the sync result. Follow the authorization steps only if the status or error calls for reconnection; use the error details to investigate other failures.
A zero-message sync is not enough to diagnose a broken connection. It may have found no new messages. Likewise, an old message still visible in Cedros does not prove the connection is currently receiving new mail.
If you see a temporary service, network, or rate-limit error, follow any retry guidance in the error and try again after the condition clears. Reauthorizing repeatedly will not repair an unavailable service or increase its limits.
Reauthorize an expired or revoked connection
You need permission to manage email provider settings and access to the intended Google account, including any sign-in verification required by your organization. Confirm the account address before beginning, and let affected teammates know you are restoring the shared connection.
- In the Google Workspace panel, read the status and error. For Reconnect Required, select Reconnect. Do not disconnect first when this button is already available.
- In the Google sign-in window, choose the same work account that the site should use. Check the full address rather than accepting whichever account your browser selects automatically.
- Complete Google's sign-in checks. Review the app identity and its requested Gmail access. The connection needs access to read mail, send messages, and modify supported mailbox states.
- Complete the consent flow only if the app and access are expected and permitted by your organization. If Google blocks the app or requires administrator approval, resolve that requirement with your administrator before continuing.
- Wait for the Google Workspace connected confirmation. Close that window and return to the original Cedros tab so the panel can refresh.
- Confirm Connected and the intended account address. Run Sync now, then complete the fresh-message and reply checks below.
If the panel instead shows Connect, read the error first. For an account that is intentionally being restored from a disconnected state, Connect starts the same authorization flow. If the site reports missing Google app configuration, ask the installation administrator to fix that prerequisite first.
Allow popups for your Cedros site if the sign-in window is blocked. If you cancel, deny access, or receive an expired or invalid sign-in result, close the old window and begin a fresh attempt from Cedros when ready. Refreshing an old callback page is not a new authorization.
Successful reconnection restores account authorization. It does not prove that all mail from the interruption has been recovered. Cedros can synchronize recent messages after reconnection; keep checking Gmail for important conversations received during the gap.
Restore Gmail write access on an older connection
An account can remain Connected while the panel says that read, archive, and delete changes currently stay in Cedros. That warning means the existing grant lacks the Gmail write access needed to synchronize those actions back.
In this connected state, the current panel shows Disconnect, not a Reconnect button. If you and your administrator intend to upgrade the permissions:
- Confirm the exact connected address and that the additional Gmail access is approved. Arrange a suitable time because disconnecting interrupts the site's connection.
- Select Disconnect in the Google Workspace panel. Check that the panel changes to a disconnected state.
- Select Connect, authorize the same account, and review the requested Gmail permissions. Follow the confirmation and return steps in Connecting your Google Workspace account.
- Confirm Connected and that the message about changes staying in Cedros is gone. Run Sync now and test a reversible read or archive change with a disposable conversation. Refresh Gmail to verify the result there too.
Do not use this disconnect-and-connect path as the first response to every sync problem. Disconnecting affects the whole site's Google connection. It does not cancel Google Workspace, move the mailbox to Cedros, or erase messages already synchronized into Cedros.
Even after permission is granted, a local change alone does not prove that Google accepted it. If message states disagree, record the example and have the administrator investigate; do not use permanent deletion to test synchronization.
Separate push-sync problems from account access
If push synchronization is configured, the panel can show a Push sync status and a Renew push sync button. These controls concern automatic notifications of mailbox changes, separately from the Google account's authorization.
First run Sync now and check a fresh message. If that succeeds while push shows Expired or Error, the account may still be usable and the notification setup needs attention.
If you manage the connection, select Renew push sync when available, then read the resulting status or error. After a successful renewal, test another new message and confirm that it appears without relying on your earlier manual sync. If renewal fails or updates still do not arrive as expected, give the error and test time to the installation administrator.
The button appears only where push is configured and the account is connected. Its absence does not mean you must reconnect, and completing Google sign-in does not by itself configure push notifications.
Verify that recovery worked
- Confirm the panel shows Connected with the intended Google account.
- Send a new message from an independent address you control to that account, using a distinctive subject such as “Cedros reconnection test.” Confirm receipt in Gmail first.
- Select Sync now in Cedros. Check for a recent successful sync, then open the test message in Email → Inbox with Focus and filters accounted for.
- Reply from Cedros to the independent test address. Check that the sender is the connected account and verify delivery at the recipient.
- If your team relies on mailbox-state synchronization, test a reversible read or archive change and confirm it in Gmail. If you repaired push sync, separately verify an automatically received update.
- Review important mail from the interruption in Gmail. Identify any messages that still need attention; do not assume the first recovery sync is a complete historical import.
Check the recipient's inbox before resending a reply that previously showed an error or uncertain result. This helps avoid sending the same response twice. Campaign and transactional delivery have their own sending setup; restoring the Google inbox connection does not verify those workflows.
Leave your working Google MX records in place. Reconnection fixes access to an existing mailbox; it is not a mail-hosting move. See Choosing Cedros email or Google Workspace if you actually intend to change hosts.
If reconnection fails again
Google authorization can stop working after access is revoked, after some Google password changes involving Gmail access, or because of account or administrator policies. Google also documents limited authorization lifetimes for certain app configurations, including apps still in testing. Have the installation administrator investigate recurring failures rather than treating regular reconnection as the permanent fix. See Google's authorization expiration guidance.
A Google Workspace administrator can review whether the app is blocked or restricted using Google's app access controls. If a consent window shows an unexpected app or a configuration error, record the message and ask the administrator to verify the configured app and site address. Do not bypass organization policy or grant unrelated access to make an error disappear.
For a useful support request, include the Cedros site, expected Google account, displayed status, error text, last successful sync time, and the time of your fresh-message test. State whether Gmail received the message, whether Sync now worked, and whether the reply arrived. Note any recent account, access-policy, or site-configuration change you know about.
Keep passwords, app credentials, authorization codes, and complete callback URLs out of support messages. Share only the message details needed to locate the test, without unrelated customer content.