> 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/ai-app-builder/preview-and-troubleshoot/inspect-app-console-and-logs.md).

# Inspect App Console and logs

Open **Console** to inspect Preview logs when a page fails to load or an interaction behaves unexpectedly.

## Investigate a problem

1. Open the affected page in Preview.
2. Click **Console** in the Preview toolbar.
3. Note the most recent messages and their timestamps in **Logs**.
4. Reproduce the problem once with a safe input.
5. Use the search field to narrow the displayed messages.
6. Expand a relevant entry where more detail is available.

![App Console showing timestamped logs, search, and Clear controls](https://3448227606-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LQ08RFAKZvFADEiXKFy%2Fuploads%2F5FginacZBCK0ybyZd6tD%2F11-console.png?alt=media)

Capture the useful error details before using **Clear**. Clearing the display is a way to reduce noise, not a fix for the underlying problem.

## Turn an error into a focused request

Include the page, the action, the expected result, and the relevant error:

> On the Tickets page, submitting the test form fails. I expected one new ticket. Here is the error and the input I used. Identify the cause before changing other pages.

Remove credentials, tokens, and private record content from logs before sharing them.

## Check the fix

Repeat the original interaction with a test record. Confirm both the app result and the source data. Before retrying a create or send action, check whether the first attempt already completed.

For workflow execution details, use the workflow run logs. For project activity, use audit logs; Preview Console is not a substitute for either.

Next: [Troubleshoot the AI Assistant](/ai-app-builder/preview-and-troubleshoot/troubleshoot-the-prompt-assistant.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 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/ai-app-builder/preview-and-troubleshoot/inspect-app-console-and-logs.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.