Overview
Start here to route Buzzy issues to the right troubleshooting guide.
Use this section to work out where a problem belongs, then move to the focused guide for that area. Buzzy issues usually fall into one of a few categories: Workspace, running apps, in-app debugging, Figma, Buzzy AI, MCP, or integrations.
Start Here
Workspace is blank, frozen, missing panels, or account/subscription access looks wrong
A previewed or published app shows an error, blank screen, missing screen, missing field, or broken action
A screen, form, view, filter, action, row context, or field binding behaves incorrectly
Figma plugin cannot connect, publish, import, or render the design correctly
Buzzy AI cannot generate, revise, create screens, or access tokens/subscription features
Builder MCP or Custom MCP is failing, exposing the wrong tools, or producing broken app changes
REST API, Code Widget, Function, or external service integration is failing
Common First Checks
Before going deep:
Refresh the browser tab or reopen the app from the Dashboard.
Confirm you are signed in with the expected Buzzy account.
Check whether the issue is isolated to one app, one screen, one browser, or one user.
Note what changed recently: a regenerated data model, renamed field, deleted screen, Figma publish, new action, new function, or MCP edit.
If a running app is affected, open the editor and inspect the screen with In-App Debugging.
What to Send Support
If you need help from Buzzy support, include:
the app URL or app ID
the screen name and, if relevant, the row or workflow you were testing
the exact error message or screenshot
whether the issue appears in Workspace, preview, published runtime, Figma, AI generation, REST/API, Functions, Code Widgets, Builder MCP, or Custom MCP
what changed recently
browser and device details for Workspace, Figma, or runtime issues
Last updated