App and Runtime Issues
Troubleshoot previewed and published Buzzy app errors, blank screens, missing screens, broken bindings, and runtime exceptions.
Last updated
Troubleshoot previewed and published Buzzy app errors, blank screens, missing screens, broken bindings, and runtime exceptions.
Runtime issues happen when an app is previewed, tested, or opened by a user. They are usually caused by missing or mismatched app configuration, data context, app actions, or custom runtime code.
app URL opens but shows a named error
preview or published app shows a blank screen
navigation opens the wrong screen or cannot find the screen
view, form, filter, or field cannot find its datatable or field
action fails or does not pass the current row
Code Widget, Function, or runtime action throws an exception
If the app shows a named error, go to App Error Codes. Error codes are grouped into:
app and route errors
datatable and field errors
component and action errors
runtime exceptions
Open the app from the Dashboard to rule out stale URLs.
Check what changed recently: deleted screens, renamed fields, regenerated data model, Figma publish, new action, new widget, or new function.
Open the affected screen in the editor.
Use In-App Debugging to inspect screen context, selected node, bindings, actions, fields, display formulas, and runtime row data.
Check whether a detail or edit screen expects the previous action to pass the current row.
After fixing the issue, preview again and rerun relevant Tests.
Last updated