Something went wrong is a broad Gmail error, not a diagnosis. Capture what Gmail was doing and whether the action completed before retrying a send, deleting data, or changing authentication settings.
Record the error in context
Write down the exact wording, any code, the time and time zone, and the action that triggered it. Distinguish opening Gmail from sending a message, uploading an attachment, or changing a setting. Take a redacted screenshot if it helps.
If the error appeared after Send, check Sent and the draft’s state before trying again. A failed confirmation display does not prove that delivery failed. If important text remains only in the open compose window, preserve it in an approved location before reloading.
Use comparisons to narrow the cause
Check the Google Workspace Status Dashboard and test a simple Gmail action in a current supported browser. If only one attachment or message fails, record that distinction. If every page fails, check the connection and browser configuration.
A different supported browser or clean profile can reveal an extension or session problem. Use your normal sign-in protections. Do not send passwords, session cookies, or verification codes to someone who asks to inspect the error.
Escalate with evidence rather than repeated resets
For a managed account, provide the administrator with the error and the successful and unsuccessful comparisons. They may need to inspect policy, service availability, or message logs. A personal account does not have the same administrative controls.
Do not turn a generic error into an instruction to erase the app, disable security software, or reset the password. Those actions have different consequences and may destroy useful evidence. If a specific follow-up error identifies an authentication, storage, attachment, or policy issue, follow the guidance for that issue and confirm the original operation only once.
Browse Gmail & Google Account help
References
Reviewed against the linked product guidance, standards, and identified vendor or public-authority guidance on October 29, 2026. Available options and screen labels can vary by account, device, region, and organization policy.