> For the complete documentation index, see [llms.txt](https://docs.buzzy.buzz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.buzzy.buzz/troubleshooting/app-error-codes.md). # 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](/troubleshooting/troubleshooting.md) 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](/troubleshooting/app-error-codes/app-not-found.md), [No App Selected](/troubleshooting/app-error-codes/no-app-selected.md), [No Screens Found](/troubleshooting/app-error-codes/no-screens-found.md), [Screen Not Found](/troubleshooting/app-error-codes/screen-not-found.md), [Unknown Path Error](/troubleshooting/app-error-codes/unknown-path-error.md) | | Datatable and field errors | A screen, component, form, filter, action, or Code Widget references missing or unset data model items. | [Datatable Not Found](/troubleshooting/app-error-codes/datatable-not-found.md), [Datatable Not Set](/troubleshooting/app-error-codes/datatable-not-set.md), [Field Not Found](/troubleshooting/app-error-codes/field-not-found.md), [Field Not Set](/troubleshooting/app-error-codes/field-not-set.md) | | Component and action errors | A screen element is missing required configuration or an action target. | [Component Missing](/troubleshooting/app-error-codes/component-missing.md), [Component Not Set](/troubleshooting/app-error-codes/component-not-set.md), [Component Settings Error](/troubleshooting/app-error-codes/component-settings-error.md), [Action Error](/troubleshooting/app-error-codes/action-error.md), [Screen Not Set](/troubleshooting/app-error-codes/screen-not-set.md), [No Context Name](/troubleshooting/app-error-codes/no-context-name.md) | | Runtime exceptions | The app loaded, but something unexpected failed while executing runtime code. | [Runtime Exception](/troubleshooting/app-error-codes/runtime-exception.md) | ## 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](/troubleshooting/in-app-debugging.md). 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](/the-building-blocks/release-tests.md). ## 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](/troubleshooting/troubleshooting.md) | | 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](/working-with-buzzy/buzzy-for-figma/troubleshooting-buzzy-for-figma.md) and [In-App Debugging](/troubleshooting/in-app-debugging.md) | | A generated app has wrong logic or broken bindings | AI output plus app structure | [Troubleshooting Buzzy AI](/working-with-buzzy/buzzy-ai/troubleshooting-buzzy-ai.md) and [In-App Debugging](/troubleshooting/in-app-debugging.md) | | A Code Widget, Function, REST call, or MCP tool fails | Extension/integration | [API and Extension Surfaces](/developing-and-extending-buzzy/api-and-extension-surfaces.md) | ## Error Reference * [Action Error](/troubleshooting/app-error-codes/action-error.md) * [App Not Found](/troubleshooting/app-error-codes/app-not-found.md) * [Component Missing](/troubleshooting/app-error-codes/component-missing.md) * [Component Not Set](/troubleshooting/app-error-codes/component-not-set.md) * [Component Settings Error](/troubleshooting/app-error-codes/component-settings-error.md) * [Datatable Not Found](/troubleshooting/app-error-codes/datatable-not-found.md) * [Datatable Not Set](/troubleshooting/app-error-codes/datatable-not-set.md) * [Field Not Found](/troubleshooting/app-error-codes/field-not-found.md) * [Field Not Set](/troubleshooting/app-error-codes/field-not-set.md) * [No App Selected](/troubleshooting/app-error-codes/no-app-selected.md) * [No Context Name](/troubleshooting/app-error-codes/no-context-name.md) * [No Screens Found](/troubleshooting/app-error-codes/no-screens-found.md) * [Runtime Exception](/troubleshooting/app-error-codes/runtime-exception.md) * [Screen Not Found](/troubleshooting/app-error-codes/screen-not-found.md) * [Screen Not Set](/troubleshooting/app-error-codes/screen-not-set.md) * [Unknown Path Error](/troubleshooting/app-error-codes/unknown-path-error.md) --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.buzzy.buzz/troubleshooting/app-error-codes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.