---
title: "Troubleshoot common errors"
description: "Find next steps for account, access, compute, SQL and MCP errors."
---

> Documentation Index
> Fetch the complete documentation index at: https://docs.pgnext.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Troubleshoot common errors

If an operation has an unclear outcome, inspect state before retrying a write. Do not include credentials in error reports.

| Symptom | Next step |
| --- | --- |
| Expired session / 401 | Sign in again in the console. For MCP, check expiry/revocation through your authorized client. |
| Access denied / 403 | Verify account, project, key scope and permission. Write access does not imply credential access. |
| Conflict / 409 | Read the message and branch/compute state. A resource may already exist or be undergoing deletion. |
| Initializing / 202 | Wait and refresh the compute; do not treat it as a failure or immediately create another. |
| Read-only mode | The service is blocking writes. Do not try another endpoint to bypass it. |
| SQL failed | Check the compute/database, role, syntax and row/time limits. |
| Timeout after a write | The outcome may still be successful. Inspect data/resource state before retrying. |
| Registration/reset email missing | Check inbox/spam. A neutral response does not confirm an account exists. New flows need the appropriate configuration and rollout. |
| MCP tools missing | Check client/endpoint and reload the session. Endpoint health does not load tools into the runtime. |
| `CONFIRMATION_REQUIRED` | Review the impact and replay exactly the same request only when the user has authorized it. |
| Data unchanged after restore | Verify branch/compute selection. A restart and subsequent SQL verification may be needed. |

## Collect investigation details

Record the action, timestamp with timezone, available HTTP/error code or request ID, and resource state with sensitive information removed. Do not send passwords, tokens, connection strings, personal data or SQL containing secrets.

For application connections, see [connection troubleshooting](/guides/connect/). For permissions, see [access layers](/integrations/access/).

Source: https://docs.pgnext.dev/reference/troubleshooting/index.mdx