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

> ## Agent Instructions
> If you are an AI assistant asked to build, change or ship a Gliss app, read the For AI agents page first (/for-ai-agents.md on this site) and follow its steps.
> Inside an app's folder, the app's own AGENTS.md is the authority; `gliss guide` prints it. Never ask the user for a secret's value.

# Troubleshooting

> Reading a diagnosis, and what to do for each kind of failure.

> [!NOTE]
>
> **Coming in the first release.** This page describes behaviour being built for the first Gliss release. Details may change before it ships.

Every [diagnosis](https://docs.glissando.dev/build/diagnostics.md) names a cause, whose problem it is, and who should act next.

## Whose problem it is

| Responsibility | Meaning | Who acts |
| - | - | - |
| `app` | The app's code or `gliss.yaml` | The app owner, usually through their AI |
| `platform` | The cluster or a Gliss component | A maintainer or IT. The builder's AI cannot fix it. |
| `unknown` | Gliss could not tell | Start with the summary and the logs |

## Causes

| Cause | Typical meaning |
| - | - |
| `crash-loop` | The app starts, then exits, again and again |
| `oom-killed` | The app ran out of memory |
| `image-pull` | The cluster cannot pull the app's image |
| `probe-failure` | The app runs but does not answer health checks |
| `pending` | The cluster cannot place the app; often capacity. See [Capacity](https://docs.glissando.dev/maintenance/capacity.md). |
| `migration-failure` | The `migrate` command failed |
| `hook-failure` | A release hook failed |
| `config-error` | A setting or secret the app needs is wrong or missing |
| `release-failure` | The release could not be applied |
| `grant-rejected` | The cluster refused the release, for example because its signature did not verify |
| `database-unavailable` | The app cannot reach its database |
| `platform-component` | A Gliss component in the cluster is unhealthy |
| `app-errors` | The app is running but returning errors |
| `unknown` | None of the above |

A page for each cause will follow as the diagnosis rules ship.


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