# Troubleshooting

> Diagnose failed deploys and stuck jobs with the request_id as your key.

## A deploy failed

1. Read `error.code` from the [error envelope](/docs/api-envelopes).
2. Look the code up in the [error codes](/docs/error-codes) catalog.
3. Copy the `request_id` and include it in any support request.
4. Retry only if the code is marked retryable.

## A job looks stuck

```bash
yalla jobs watch --env production
```

> [!NOTE]
> Logs and metrics may be unavailable while an adapter is still wiring up. The CLI shows an honest "unavailable" state rather than fabricated data.