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

# Troubleshooting

> Resolve sign-in, connection, database and deployment problems.

> [accordion] I cannot complete my first sign-in
>
> Select **Forgot password?** in Console and enter your confirmed account email. Use the email link to set your password, then complete any required MFA challenge. Account approval and workspace invitations are separate from password setup.

> [accordion] My workspace or website is missing
>
> Check the account and accepted invitation. Ask an administrator to review current membership, website grants and resource status. A contact email or pending invitation does not grant access.

> [accordion] Neon connects but my database is not deployed
>
> Connections currently manages the API key and reads project inventory. Create the database in your own Neon account. SQL access and automatic application bindings are separate capabilities.

> [accordion] Neon project inventory is unavailable
>
> Check the API key's validity and permissions. For a project-scoped key, enter the exact project ID. Refresh after correcting access; no platform key or paid-capacity fallback is used.

> [accordion] An existing database browser does not open
>
> Wait for the reported connection result, then use its retry action after a failure or timeout. If it still fails, ask your operator to check the database state, access grant and gateway. Do not delete the database to resolve a browser error.

> [accordion] No repository source or build action is available
>
> Git self-service is not generally available. Your operator must activate the repository authorization, Hosting, registry and build-service prerequisites. A visible Builds page or saved repository URL does not admit a public build.

> [accordion] My build succeeded but the application is not ready
>
> Open **Publications**, follow its deployment status and **Rollout operation**, then check the application endpoint. Successful build output and healthy deployment are separate results.

> [accordion] An action is accepted but the resource has not changed
>
> Open the existing operation and inspect its progress and errors. If its result is uncertain, use that request's retry or ask an operator to reconcile it before submitting another change.

> [accordion] Mail was accepted but has not arrived
>
> Check message status, recipient results and events. Provider acceptance is not delivery. Reconcile an unknown result instead of sending it again as a new request.

> [accordion] Console asks me to sign in again
>
> Complete central sign-in. Console has its own host-specific application session. Start an interrupted provider authorization again from Console rather than reusing an old callback URL.

> [accordion] OAuth returns 401
>
> Check token expiry, audience, scope and revocation. Registered Auth and Studio protocol addresses remain compatibility contracts; Console's browser domain does not replace them.

> [accordion] Usage is unreported or storage remains allocated
>
> Missing telemetry does not mean zero usage. Stopping or deleting an application can retain storage and its accounting. Permanent purge is a separate administrator action.

## Report a problem

Include the resource ID, operation or request ID, timestamp, attempted action and displayed error. Say whether it happened in Console, an API client or the application. Remove credentials, cookies, private connection strings and message content.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.