> For the complete documentation index, see [llms.txt](https://docs.pixiebrix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pixiebrix.com/activating-mods/troubleshooting.md).

# Troubleshooting

Troubleshooting Mod Activation

Having issues with activating your mods? Try these questions. If it doesn't help, feel free to reach out via live chat or [send an email to support](mailto:support@pixiebrix.com).

### You cannot find the PixieBrix extension using Google or the Chrome Web Store

Contact your PixieBrix admin for which installation instructions to follow. You may need to follow instructions for\
[Installing the PixieBrix Chrome Browser Extension](/how-to/installing-the-pixiebrix-chrome-browser-extension.md) or

[Linking Your PixieBrix Account](/activating-mods/linking-your-pixiebrix-account.md) if your company already installed it.

### You do not see the “Team deployments are ready to activate” banner

* Verify that you connected the correct email address by looking at the upper right corner
* If the correct email address is not showing, go to [https://app.pixiebrix.com](https://app.pixiebrix.com/), click the email address in the upper right, and click “Logout".

### The mods don't appear or seem to be work even after you've activated them

* Refresh the page and see if that fixes the problem
* Open the PixieBrix browser extension. From [https://app.pixiebrix.com](https://app.pixiebrix.com/) you can open it by clicking “Open Browser Extension”
* Verify the brick is listed on the Active Bricks page and has the status "Active"
* Perform one of the following actions to resolve the issue:
  * If the brick is not listed: contact your PixieBrix admin to ensure you've been granted access to the brick
  * If the status shows a "Grant Permissions" button, click the "Grant Permissions" button and accept the permissions in the Chrome Permissions prompt
  * If the status is "Active", click "Uninstall" and activate it again following the instructions in [Activating Your Assigned Mods](/activating-mods/activating-your-assigned-mods.md)

### How to reload the extension

To reload the extension:

* Open the PixieBrix browser extension. From [https://app.pixiebrix.com](https://app.pixiebrix.com/) click “Open Browser Extension"
* Click the Settings item in the sidebar\\

  <figure><img src="https://2274778196-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fq123bF1HPQPV35s5vHa1%2Fuploads%2Fgit-blob-dfdeed804d0ccfe5282b25f4d953df01dd099da1%2Fextconsole-nav-settings.png?alt=media" alt="Settings in the browser extension sidebar" width="220"><figcaption></figcaption></figure>
* Scroll to the bottom of the page and click the "Reload Extension" button


---

# 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://docs.pixiebrix.com/activating-mods/troubleshooting.md?ask=<question>&goal=<user_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.
