If a file opens for a colleague but not for you, something saved in your browser may be in the way. A repair clears the settings and caches every app keeps in this browser, then you open the file again. It works from this page even when the editor itself will not start.
What a Repair Clears
- Settings kept only in this browser, such as panel positions and light or dark appearance. Preferences saved to your account, such as panel opacity, come back on the next load.
- Tips and banners you dismissed in this browser, which may show again once.
- The cached list of recent files, which reloads from the server.
- Saved share-link passwords, so a protected link asks for its password again.
What a Repair Always Keeps
- Your files. Files stored on the server stay there, and a repair never touches them.
- Your guest identity. If you use every app without an account, the files you made belong to an identity saved in this browser. A repair keeps it, so your files stay in your list.
- Offline files. These exist only in this browser, so a repair leaves them alone.
- Your sign-in. A repair never signs you out.
Copy Diagnostics
Copy Diagnostics copies a short report about this browser: whether storage and cookies work, whether the browser's database opens, and whether the browser is up to date. Paste it into a message to support so we can see what is going on. It never includes what is in your files, and it carries only the start of a guest id. From the editor it also includes the file's address and, if you are signed in, your account id.
When a file fails to load, the editor offers the same two buttons on its error screen while you are online, and its report also says how far the load got.
If It Still Does Not Load
Work through the "will not load" article for your app first.
If you are a guest, signing in moves your files to an account, which also rules out anything saved in this browser.
Works the same in liveknowledge.
Was this article helpful?
Still need help?
Try Troubleshooting, or tell us what you were trying to do.