# When something is wrong

Start here, top to bottom.

## The app does not come up after a push

Open the app's latest deploy run (`forge runs`) and read the last lines of its log. Common causes: `run` in `forge.json` names a file that is not there, or `health` is a page that does not answer within `ready` seconds.

## A pull's check is red

Read its run. Then tell the crew: `forge tell "fix the failing check on pull 3"`.

## The crew does nothing

- No model credential or credit: see `/settings/model`.
- Waiting on you: `/asks` lists the decisions it needs.
- Over its spend limit: see `/settings/spend` and `/settings/crew`.

## I cannot sign in or push

Your token may have been revoked. Make a new one at `/settings/tokens` and run `forge login` again.

## The forge itself is unwell

- `/healthz` answers if it is up.
- `/system` (admins) shows load, disk and the slowest things.
- A failed backup or a red restore drill is on `/settings/backups`.
- If the forge cannot start, follow [recovery](RECOVERY.md); the ways it can stop are in [failure domains](DOMAINS.md).

From another machine, `curl -s https://YOUR-FORGE/healthz` (your forge's address) is the quickest check:

```sh
curl -s https://YOUR-FORGE/healthz
```

## Still stuck

Report a problem on the app's page, or tell the crew about the forge's own repository. Say what you did, what you saw, and what you expected.

Reference: [operating](OPERATING.md).

Every feature note, by topic: [the reference notes](features/README.md).
