> 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/jet-bridge-deployment/logs-and-troubleshooting.md).

# Troubleshooting

Start with the symptom, then inspect the part of the release path responsible for it.

| Symptom                                          | Guide                                                                                                                        |
| ------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------- |
| Preview has a change that users cannot see       | [Published changes are missing](/jet-bridge-deployment/logs-and-troubleshooting/published-changes-missing.md)                |
| User cannot sign in or sees the wrong access     | [Published app access fails](/jet-bridge-deployment/logs-and-troubleshooting/published-app-access-fails.md)                  |
| Custom address does not load correctly           | [Troubleshoot a custom domain](/jet-bridge-deployment/custom-domains/troubleshoot-a-domain.md)                               |
| Data, actions, or self-hosted services fail      | [Diagnose resource and deployment errors](/jet-bridge-deployment/logs-and-troubleshooting/resource-and-deployment-errors.md) |
| App works directly but fails inside another site | [Embed an app](/jet-bridge-deployment/share-and-embed/embed-an-app.md)                                                       |

## Collect a reproducible report

Record the app, environment, exact address, affected role, action, time with timezone, expected result, and actual result. Include the relevant app version and platform version when known.

Use [System logs](/access-and-sharing/audit-logs-privacy-and-security/investigate-system-logs.md) for available diagnostic messages and [the audit trail](/access-and-sharing/audit-logs-privacy-and-security/review-the-audit-trail.md) for available activity. Remove credentials and unnecessary personal data from shared evidence.

## Choose the right next step

Compare the problem with the last working configuration. Make one targeted correction, then repeat the same failed check.

If recovery is needed, choose between [app version history](/ai-app-builder/test-and-publish/version-history.md), [environment restoration](/jet-bridge-deployment/environments.md), and the affected data system's recovery process. These have different scopes.

For AI generation or revision failures, use [AI App Builder troubleshooting](/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/jet-bridge-deployment/logs-and-troubleshooting.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.