When to use
After deploys, restarts, environment variable changes, or incident reports.Fetch logs
Logs are recent output, not a full history. To audit past deploys, use build history:
GET /api/apps/:appId/builds.Options
Common problems
The app errors but logs are empty
The app errors but logs are empty
The process may never have started. Check status with
GET /api/apps/:appId and look at build history — the failure may be in the build step, not the runtime.Logs show nothing after updating environment variables
Logs show nothing after updating environment variables
Variables are injected at startup. Restart the app (
POST /api/apps/:appId/restart) and fetch logs again.I need more lines
I need more lines
Increase
tail (e.g. ?tail=1000). If the incident already passed, add ×tamps=true to align output with the timeline.Next steps
Restart an app
Restart the process after config changes.
Update environment variables
Change app runtime configuration.