App Error Codes

App error codes appear when a running Buzzy app cannot resolve the app, screen, datatable, field, component, action, or runtime context it needs. These are runtime/app issues, not general Workspace account issues.

Use this page when a previewed or published app shows an error screen, a blank runtime state, or a named app error. If the Workspace editor itself is blank or frozen, start with the Troubleshooting Overview instead.

How to Read These Errors

Most app errors fall into four groups:

Group	What it usually means	Common errors
App or route errors	The URL, app, screen, or route cannot be resolved.	App Not Found, No App Selected, No Screens Found, Screen Not Found, Unknown Path Error
Datatable and field errors	A screen, component, form, filter, action, or Code Widget references missing or unset data model items.	Datatable Not Found, Datatable Not Set, Field Not Found, Field Not Set
Component and action errors	A screen element is missing required configuration or an action target.	Component Missing, Component Not Set, Component Settings Error, Action Error, Screen Not Set, No Context Name
Runtime exceptions	The app loaded, but something unexpected failed while executing runtime code.	Runtime Exception

Fast Triage

1. Open the app from the Dashboard. This rules out stale deep links and deleted screen URLs.

2. Check what changed recently. Renamed fields, deleted screens, regenerated data models, updated Figma publishes, or changed actions are common causes.

3. Use in-app debugging. In the editor, inspect the affected screen or selected node with In-App Debugging.

4. Check data context. Detail screens, edit forms, sub-tables, and row actions often require the previous action to pass the current row.

5. Check bindings. Views, forms, filters, fields, buttons, and widgets must point to current datatables, fields, screens, and actions.

6. Republish or retest. After fixing the binding or configuration, preview the app again and rerun any relevant Tests.

Workspace vs Runtime

Symptom	More likely area	Where to go
Workspace editor does not load, subscription access is wrong, or panels are unavailable	Workspace/account	Troubleshooting Overview
App URL opens but shows a named error	Runtime/app	The matching error page below
A Figma-published app is blank or visually wrong	Figma/plugin or screen structure	Troubleshooting Buzzy for Figma and In-App Debugging
A generated app has wrong logic or broken bindings	AI output plus app structure	Troubleshooting Buzzy AI and In-App Debugging
A Code Widget, Function, REST call, or MCP tool fails	Extension/integration	API and Extension Surfaces

Error Reference

• Action Error

• App Not Found

• Component Missing

• Component Not Set

• Component Settings Error

• Datatable Not Found

• Datatable Not Set

• Field Not Found

• Field Not Set

• No App Selected

• No Context Name

• No Screens Found

• Runtime Exception

• Screen Not Found

• Screen Not Set

• Unknown Path Error