> For the complete documentation index, see [llms.txt](https://help.distro.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.distro.so/integrations/chrome-extension/troubleshooting.md). # Troubleshooting ## Distro won't open on this page Try an ordinary website. Chrome restricts extensions on its internal pages and the Chrome Web Store. If you installed or updated Distro while a website was already open, refresh that website and try again. ## A link or sales handoff is missing Check the connected account in the extension's **Settings**. Confirm the link exists in the same Distro workspace. For group links, check that you're a participant. For sales handoffs, ask your admin to check that the Outbound Router is active and that you're an allowed booker. Use the refresh or retry action after access is updated. ## Typing `di/` does nothing Use a supported message body or event description, not a subject, recipient field, or search box. Check **Settings → Browser integrations → Keyword detection**, including the switch for that app. Then refresh the webpage and try again. ## Times won't insert into my email Keep the original Gmail draft open while selecting times. If the draft has closed or the insertion is no longer available, choose **Copy times** and paste the result into your message. ## My meetings show the wrong time Check **Settings → Meeting timezone**. Browser time and account time can differ. Changing the display timezone doesn't reschedule a meeting. ## Distro asks me to sign in again Complete sign-in and reopen the extension. For a temporary connection error, retry when the connection returns. If sign-in repeatedly fails, include the visible error message when contacting your Distro support contact. When reporting an issue, include the app you were using, what you tried, and whether refreshing helped. A screenshot of the error is useful; remove recipient details or private message content first. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.distro.so/integrations/chrome-extension/troubleshooting.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.