General Mod Troublshooting

Follow these actions for debugging issues with mods

If your mod isn't working as expected, any number of things could be happening. Look for common issues and solutions, or follow the debugging steps below to troubleshoot mod issues. If you're stuck, you can always reach out to [email protected] for help, or post in our Developer Community.

The mod I created isn't appearing on my page.

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.

My users aren't receiving a deployed mod.

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.

Troubleshoot Best Practices

If your mod isn't working as expected, follow these steps.

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.

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.