> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/classic-app-builder/preview-and-publish/troubleshoot-a-classic-app.md).

# Troubleshoot a Classic app

Applies to **Classic App Builder**. Screens and recordings in this section show the Classic interface.

Trace a problem from the visible component to the value, action, or data request responsible for it.

| Symptom                             | Check first                                                                    |
| ----------------------------------- | ------------------------------------------------------------------------------ |
| Component is empty                  | Resource result, active filters, field mapping, and empty-state configuration. |
| Form shows the wrong record         | Selected row, bound field, and record identifier.                              |
| Filter has no effect                | Referenced output, value type, comparison, and other filters.                  |
| Button appears to do nothing        | Click Action, required inputs, confirmation, and operation result.             |
| Data changes but the UI looks stale | Post-action refresh and the component's data source.                           |
| A user sees different content       | Identity, team, dynamic filters, visibility, and enforced permissions.         |
| Published app differs from Preview  | Target environment, published address, and release state.                      |

## Reproduce and isolate

1. Record the page, component, user role, environment, and failure time.
2. Use one synthetic record and a repeatable action.
3. Inspect the source value before checking the target binding.
4. Inspect action inputs before changing the action.
5. Check the resource result and available logs.
6. Make one targeted correction and repeat the same test.

For UI bindings, use [Data binding and variables](/classic-app-builder/binding-and-values.md). For behavior, use [Actions and logic](/classic-app-builder/actions-and-logic.md). For release problems, use [Publish & Deploy troubleshooting](/jet-bridge-deployment/logs-and-troubleshooting.md).

A hidden control and a denied request are different outcomes. Repeat allowed and denied [access tests](/access-and-sharing/overview/test-access.md) after changes.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.jetadmin.io/classic-app-builder/preview-and-publish/troubleshoot-a-classic-app.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.