> 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/resource-and-deployment-errors.md).

# Diagnose resource and deployment errors

Trace the failed operation from the published app to the resource or service responsible for it.

## Isolate the failure

1. Record the environment, user role, page, action, and time.
2. Determine whether the app itself loads.
3. If loading works, identify the query, resource, API, or workflow used by the failing action.
4. Check the configured connection, credential scope, and required network path.
5. Reproduce with a safe read or synthetic test record.
6. Inspect the relevant logs before changing configuration.

A successful connection test is not proof that every query or write is authorized. Check the specific failed operation and identity.

## Use the deployment-specific checks

| Deployment             | Diagnostic path                                                                                                                                                                                                                                          |
| ---------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Cloud                  | App [System logs](/access-and-sharing/audit-logs-privacy-and-security/investigate-system-logs.md), resource settings, and relevant provider diagnostics.                                                                                                 |
| Self-hosted Jet Bridge | Bridge service logs, [Common Problems](/jet-bridge-deployment/cloud-jet-bridge-and-on-premises/jet-admin/common-problems.md), and [Configuration](/jet-bridge-deployment/cloud-jet-bridge-and-on-premises/jet-admin/configuration.md).                   |
| On-Premise             | [Service Health Check](/jet-bridge-deployment/cloud-jet-bridge-and-on-premises/on-premise/service-health-check.md), affected service logs, and [Common Problems](/jet-bridge-deployment/cloud-jet-bridge-and-on-premises/on-premise/common-problems.md). |

Use the actual service URLs from your environment when following health checks. A service responding successfully does not establish that authentication, resource access, or the full user flow works.

Share redacted errors and reproduction steps with the responsible operator. After correction, repeat the failed operation and [the affected release checks](/jet-bridge-deployment/publish-your-app/verify-a-release.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/resource-and-deployment-errors.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.