# General Mod Troubleshooting

As with any type of development, sometimes your mod won't work the way you expect and you'll need to debug to figure out how to make it work as desired. 

This page has some helpful tips for troubleshooting, and we'll be adding more so feel free to bookmark this page. 

{% hint style="info" %}
If you can't find the answer you need here, feel free to message us with the live chat in the bottom left, or post in the [PixieBrix Slack Community](https://slack.pixiebrix.com/).
{% endhint %}

### Determining Which Brick Is Failing

When you run an action or enhancement from the Page Editor, the Brick Overview Panel will show the status of each brick:

* Green Check: the brick succeeded
* Red Exclamation Mark: the brick raised an error
* Grey Dash: the brick was skipped due to a condition
* Blue Clock: the brick is currently running

### Insufficient Browser Permissions

*I am seeing this error “Insufficient browser permissions to make request. Specify an integration to access the API or add an Extra Permissions rule to the mod (previously referred to as extension.” How can I fix it?*

<figure><img src="/files/iToU7XKARUurFW64AWYw" alt=""><figcaption></figcaption></figure>

**Answer:** Navigate to the first brick in your mod. If you scroll down the configuration panel, you will find a blue button that says: **Extra Permissions**

<figure><img src="/files/8Y8U4wIoYq2BrWJh7vws" alt=""><figcaption></figcaption></figure>

Extra Permissions just records that PixieBrix needs permissions to make calls to the API provider even though the mod is not running on that page

### Troubleshooting Best Practices

If your mod isn't working as expected, follow these steps.&#x20;

**Check for errors in the Page Editor Logs**

Click on the mod in question and look through each mod component to view Logs and look for any errors that could indicate what's failing in the mod.

<figure><img src="/files/GyedPLhO0IXIdHdUTGS5" alt=""><figcaption></figcaption></figure>

**Review the Data Panel while running a mod to confirm expected inputs and outputs**

While running the mod, step through each bricks' output and input tabs from the Data Panel to see what each brick is receiving and returning. This can help you identify anything that might not be parsing correctly and therefore causing errors or unexpected issues. For instance, if you're extracting data from a LinkedIn page, then asking ChatGPT to categorize the info, then send that response to an API, check each brick to confirm you are getting the correctly scraped information and ChatGPT is returning a response that makes sense for the API schema.

### FAQs

<details>

<summary>The mod I created isn't appearing on my page.</summary>

If you don't see a mod appearing in your browser (via Sidebar, context menu, button, quick bar, or trigger), check that the triggers for each mod component inside the mod are inclusive of the current URL.&#x20;

<figure><img src="/files/2uwzJVAuETRkjRHHLRM2" alt=""><figcaption></figcaption></figure>

</details>

<details>

<summary>My users aren't receiving a deployed mod.</summary>

Confirm the users are part of a group that is assigned to the deployment. If so, confirm that they have the PixieBrix Chrome extension installed and they are logged in to PixieBrix when they visit app.pixiebrix.com.

</details>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.pixiebrix.com/how-to/troubleshooting/general-mod-troubleshooting.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.