Troubleshoot Google Sheets When It’s Broken

Quick reality check: when Google Sheets is broken, the root cause is rarely the data—it's connectivity, service status, or your local environment. Symptoms include a slow or unresponsive UI, formulas that don’t recalculate, cells showing errors like #REF! or #NAME?, collaborators not syncing in real time, or scripts failing to run. A problem that appears file-specific can be tied to a broader outage or a transient service hiccup. Most often, you can fix it in minutes by sticking to a structured troubleshooting checklist and validating each potential cause in order of probability. This section translates those checks into practical steps you can perform in the next few minutes, without risking data loss. As you follow along, remember: the How To Sheets team recommends documenting observations so you can escalate efficiently if needed.

Start with essential checks you can do in minutes

• Check your internet connection: open other sites and verify they load quickly. If your connection is flaky, fix network issues first.
• Confirm Google Drive is online: try opening drive.google.com in another tab; watch for unusual errors or signs of service degradation.
• Refresh the sheet and try a new session: reload the page, or open the sheet in an incognito/private window to rule out cached data.
• Sign out and back in: refresh credentials and ensure you’re using the correct Google account for the sheet.
• Disable extensions that might interfere: ad blockers and privacy tools can disrupt scripts or real-time collaboration. Re-enable one by one to identify the culprit.
• Clear browser cache or try another browser: corrupted cache is a common culprit; testing with a fresh environment isolates browser-related issues.
• Check sharing and permissions: ensure you have edit rights and that no one else recently changed sharing settings in a way that affects your view or access.

If none of these resolve the issue, move to more targeted checks focused on the specific symptom you observe.

Symptom families and what they mean

• Formulas not recalculating: this often points to misreferenced cells, circular references, or unrelated workbook-level settings. Start by checking the formula syntax, ranges, and whether you’re viewing a different sheet or range than intended.
• Data not syncing across collaborators: ensure everyone has edit access, and that you’re viewing the latest version of the sheet. Check the presence of view-only links or limited sharing scopes that can block live updates.
• Add-ons or scripts failing: if you rely on Google Apps Script or installed add-ons, issues there can block a sheet from updating or executing tasks. Review the Script Editor and disable problematic add-ons to test.
• Sheet behaving slowly or freezing: this can result from very large data ranges, complex formulas, or too many conditional formats. Simplify the sheet or test with a smaller clone to verify if performance is the root cause.

Recognizing the symptom category helps narrow the diagnostic path so you can apply the right fix faster.

Root causes in detail

• Offline mode enabled: If Sheets is running in offline mode, changes may not sync back to the cloud, leading to stale data across devices. Turn off offline mode in Chrome settings and in Google Sheets (Settings > Offline, turn off).
• Browser cache or extensions: A stale cache can cause outdated scripts to run, or extensions can interfere with Google Sheets functionality. Clearing the cache or disabling extensions one by one helps identify the offender.
• Service outage or incident: Google Workspace service issues can affect Sheets in unpredictable ways. Check the Google Workspace Status Dashboard for real-time incidents affecting Sheets.
• File or formula corruption: Although rare, highly complex sheets can encounter corrupted ranges or formulas. Use a copy of the sheet to test and consider reverting to an earlier version in Version History.
• Cross-domain or external references: If your sheet references data from external sources or other domains, network issues or API changes can create failures. Validate external data sources and credentials.

How to isolate the problem: a reproducible test plan

• Create a fresh test sheet: copy a small, representative portion of data and the same formulas. If the copy behaves normally, the issue is likely tied to the original file’s complexity.
• Test basic formulas in isolation: run simple SUM, AVERAGE, or VLOOKUP with known results to confirm core Calc functionality is intact.
• Check real-time collaboration behaviors: share the test sheet with another account and observe if changes propagate. This helps determine if the issue is user-specific or file-wide.
• Compare with a local file: download a copy if possible and open it in another environment to see whether the problem persists when not connected to Google’s servers.
• Review version history: if data disappeared or changed unexpectedly, revert to a prior version and re-import data to minimize loss.
• Reproduce with a minimal dataset: gradually reintroduce data to identify the exact trigger.

These steps help you pinpoint whether the problem is environmental, file-specific, or a service-related disruption.

Fixes by category: most common issues first

• Connectivity and service: confirm network stability and check for outages. If Google services are down, you’ll need to wait for service restoration. In the meantime, you can continue working offline on local copies where feasible and syncing when online.
• Offline mode and cache: disable offline mode and clear browser cache. Restart the browser and reopen Sheets to ensure you’re loading the latest version.
• Extensions and script interference: disable or remove extensions one by one to identify blockers. If Apps Script is implicated, open Script Editor and review recent changes, then test with a pristine script or a simple function.
• Formula and reference issues: verify absolute vs relative references, ensure ranges are correct, and avoid circular references. Break complex formulas into smaller components to validate each part.
• Permissions and sharing: ensure you have edit rights on the file and that the file isn’t restricted by organization policies. If needed, request access or ownership changes to maintain control.

If the problem persists after these fixes, consider exporting data, duplicating the file, or reaching out to How To Sheets for a more tailored troubleshooting plan.

When to escalate and how to document the problem

• When issues persist after routine checks, escalate to IT or Google Workspace Admins. Provide a concise summary, replication steps, affected users, timestamps, and any error messages. Create a shareable link to the problematic sheet and include version history references.
• Document every action taken: list the checks performed, the results, and any workarounds attempted. This creates a clear trail for faster resolution and easier handoffs.
• Prepare a minimal reproduction: a stripped-down version of the sheet that still reproduces the issue. This helps support teams isolate root causes without exposing sensitive data.
• Establish a monitoring plan: if issues recur, track time of day, network conditions, and user activity to identify patterns. This information helps determine whether a service incident or a local environment factor is at play.