> 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/in-app-debugging.md). # In-App Debugging Use this page when a Buzzy app screen, form, view, filter, action, field binding, row context, display formula, or runtime state does not behave as expected. The Buzzy **Debug** tab and debug agent show what the editor and runtime understand about the selected screen or node. Use them to interpret semantic issue patterns, inspect data binding, and choose the right fix. ## Debug tab sections The Debug tab is contextual, so not every section appears for every selection. Common sections include: | Section | What it tells you | | -------------------------- | ------------------------------------------------------------------------------------------------------ | | **Selection** | What Buzzy thinks you have selected and the scope being inspected | | **Data binding** | Which table, field, sub-table, or row context the selected node uses | | **Issues** | Problems found on the current selection, plus issues found in descendants when you are at screen scope | | **Visibility and display** | Conditions that control whether the item appears | | **Runtime context** | The surrounding route, row, or view context Buzzy can infer | | **Row data** | Record-level context when the selection belongs to repeated content or a record-driven screen | | **Table fields** | Available fields for the active table or view context | ## Severity levels Issue severity is grouped into three levels: | Level | Meaning | | ----------- | ------------------------------------------------------------ | | **Info** | Useful context or a condition that may explain behaviour | | **Warning** | Something looks suspicious and may cause a bug | | **Error** | Buzzy found a concrete misconfiguration or broken dependency | In general, fix **Errors** first, then review **Warnings**, then use **Info** items as context when you need to understand why something is behaving a certain way. ## Runtime context Runtime context helps explain why a component may behave differently depending on where it is used. This can include: * whether the node expects a parent row context * which table or sub-table is active * whether the node sits inside a repeated view * whether display rules, visibility rules, or actions depend on route or record state When an issue mentions missing context, it usually means the selected node expects a parent view, row, or binding that is not available in its current position. ## All semantic issue types and fix options This table lists the semantic issue types currently defined in the screen analyzer, together with the fix options attached to each issue guide.

Issue type	What it means	Fix options
Missing view table setting	A view component has no selected datatable, so it cannot load rows.	Bind the view to the correct table.
Missing form table setting	A form component has no selected datatable, so its fields have no form data source.	Bind the form to the correct table.
Missing filter table setting	A filter component has no selected datatable, so its filter fields have no source table.	Bind the filter to the correct table.
Missing filter context setting	A filter component has no filter-context name, so views cannot reference its output.	Set the filter context name.
Missing field selection	A field node has no selected field binding.	Bind the node to the correct field.
Invalid table reference	The configured datatable reference does not exist in the current app data model.	Rebind the component to the correct table.
Invalid field reference	The configured field reference does not exist in the current data model.	Rebind the node to the correct field.
Sub-table field bound to non-sub-table field	A sub-table field node is bound to a field that is not actually a sub-table field in the data model.	Possible solutions: 1. Bind the sub-table node to the correct sub-table field. 2. Replace this sub-table node with the correct node type for the selected field. 3. Remove this sub-table node if it is not needed.
Field requires screen row context	This read/summary/edit/value field has no local row context and would rely on a row being passed into the screen at runtime.	Possible solutions: 1. Fix the action that opens this screen so it passes the current row. Best when the screen is meant to open as a detail screen for a selected row. 2. Put this content inside a local view, form, or sub-table that provides row context. Best when this node should get its row from nearby screen structure instead of navigation.
Field immediate context mismatch	The field belongs to a different datatable than the node’s immediate semantic context.	Possible solutions: 1. Rebind the node to the correct field. Best when the node is simply pointing at the wrong table field. 2. Put this content inside the correct local view, form, or sub-table context. Best when the field is structurally outside the wrapper that should provide its row context.
Subtable requires parent row context	This subtable needs a parent row context and would rely on a screen row being passed at runtime if no local row context exists.	Possible solutions: 1. Fix the action that opens this screen so it passes the parent row. Best when the screen is meant to open in the context of a selected parent record. 2. Put the sub-table inside the correct local parent-row context. Best when the sub-table should inherit parent context from nearby screen structure instead of navigation.
Insert field outside capture form	An insert-mode field is outside a capture-form layout, so it cannot behave as a valid insert field.	Possible solutions: 1. Change the field to a non-insert mode. Best when this is an isolated field on a display-oriented screen. 2. Wrap this branch in a capture form. Best when several insert fields or submit actions in the same branch suggest missing form structure.
Form initial mode layout missing	The form starts in a mode whose layout is missing.	Possible solutions: 1. Add the missing form layout. 2. Change the form initial mode to one that already has a layout. Best when the existing layouts are correct and the start mode is the wrong part.
Submit action outside capture form	A submit action is outside a capture-form layout.	Possible solutions: 1. Move the submit action into the capture form. Best when the form structure already exists and only the action placement is wrong. 2. Wrap this branch in a capture form. Best when nearby fields and actions show the whole branch is missing form structure.
Form mode action outside form	A form mode action is outside a form component.	Wrap this branch in a form.
Form mode target layout missing	A form mode action points to a form mode whose layout does not exist.	Possible solutions: 1. Add the missing target layout. 2. Change the action to a mode that already exists. Best when the intended destination mode was configured incorrectly.
View results missing repeat	The view results layout has no repeated row node.	Add the repeated row inside the view results.
View results has multiple repeats	The view results layout has more than one repeated row node.	Remove the extra repeated row structure.
View results layout missing	The view has no results layout.	Add or restore the view's results layout.
View no-results layout missing	The view has no no-results layout.	Add or restore the view's empty-state layout.
View has no renderable layout	The view has neither a results layout nor a no-results layout, so it cannot render meaningful view output.	Possible solutions: 1. Add or restore the view's results layout. 2. Add or restore the view's empty-state layout.
View paging action outside view	A paging action sits outside a view results layout.	Move the paging control into the view controls area and outside the repeated row.
View paging action inside repeat	A paging action is inside the repeated row node, where it should not be.	Move the paging control into the view controls area and outside the repeated row.
View may need sub-table field	A generic view is querying a child table inside a parent row context where a declared sub-table relationship already exists.	Replace the generic view with the matching sub-table field.
Filter action outside filter component	A filter action is outside a filter component.	Wrap this branch in a filter component.
Filter field outside filter component	A filter-mode field is outside a filter component.	Possible solutions: 1. Wrap this branch in a filter component. Best when the field and nearby filter behavior belong inside a filter wrapper. 2. Change the field to filter mode after moving it into the correct filter context. Best when the field is meant to stay as part of a filter UI.
Filter field mode mismatch	A field inside a filter component is not using filter mode.	Change the field to filter mode.
Filter context not consumed on this screen	The filter context name is not currently referenced by any known consumer in static analysis.	Align the filter context name with the intended consumer.
Filter context has no same-screen consumer	The filter context is not consumed by any same-screen view.	Possible solutions: 1. Align the filter context name with the intended consumer. 2. Add the missing same-screen consumer for this filter context.
View filter context missing provider	A view references a filter context that has no same-screen provider.	Possible solutions: 1. Align the filter context name with the intended provider. 2. Add the missing same-screen filter provider.
Unknown action target	An action targets a screen that does not exist.	Rebind the action to a valid screen.

For the task-oriented walkthrough, see [Debugging with the Debug Tab and Debug Agent](/getting-started-with-buzzy/new-buzzy-ai-v3/6.-debugging-with-the-debug-tab-and-agent.md).