Read logs and errors
Read what your running app prints and where it crashes.
When your app misbehaves, the logs and the grouped crashes tell you why. Open them in the Console or ask your agent.
- Open your app in the Console.
- Read Logs for the fleet’s newest output first.
- Read Errors for crashes grouped by cause.
Where each output lives
| Output | Where it lives |
|---|---|
| Running app output | Console → Logs, newest first (stdout and stderr). |
| Build output | On the deploy: expand it in Deploys view. |
| Crashes | Console → Errors, grouped by fingerprint with counts and last-seen times. |
Ask your agent for app_logs, deploy_log, or app_errors when you prefer chat. Triage (resolve, ignore, reopen) happens through your agent. Outer also emails you about failed deploys and error spikes: Get email alerts. How agents read them: Read logs and errors after deploys.