Start here
A connected account belongs to a particular person or deployment configuration. Signing into Deepwater with Google does not, by itself, prove that Gmail, Calendar or Drive synchronization has all the permissions it needs.
Check and recover
- Open Settings → Integrations in the intended workspace. Check which account is connected and any status or error shown for that connection.
- Confirm that the connected account actually contains the email, calendar or file you expect to see. Check the source application directly before troubleshooting the copy in Deepwater.
- If Deepwater requests reconnection or an additional permission, reconnect the intended account and review the requested access. For example, reading email and sending email are different permissions.
- After reconnection, use the available sync controls and allow the request to finish. Refresh the affected screen and compare the same date range.
- If a shared organization policy blocks consent, your Google Workspace administrator may need to review the connection. Repeated reconnection attempts cannot override that policy.
For self-hosting, the operator should check the configured application URL, OAuth redirect addresses and server credentials. Users should not paste provider secrets into a support conversation.
Check before retrying a send
An email permission issue, an approval requirement and a delivery failure are different problems. Check the sequence or message state before retrying so you do not send the same follow-up twice.
When to contact the team
Include the provider, affected feature, visible connection status, last known successful sync and exact error. Say whether the item is present in the provider’s own application.
Related: Signal meeting troubleshooting.