Call FIRST when debugging a runtime problem (a 500, a failed request, a blank page, 'it doesn't work'), before theorizing. Sources:
- 'server' (default): the dev backend's request logs, last hour (method, URL, status, duration, log lines), background jobs included; log_reference_id: one request in full.
- 'browser': console output and client network requests (`⇄ METHOD url → status`, error body of failed ones: CORS, timeouts, third-party calls) from the user's open editor (~1 hour; empty if none); a line's `ref=<id>` is a 'server' log_reference_id.
- 'background': background work in the preview and the published app: schedules and next run, runs in progress, runs long or cut off at the 15-minute limit in 7 days ('still running?', 'timed out?').
- 'published': the PUBLISHED app's backend logs (kept 90 days), oldest first, last hour by default; from/to (ISO 8601), filter (literal substring), limit (default 200), cursor (get_guides('prod-backend-logs')).
- 'push': push sends, newest first, per device, delivered or not; from/to, subscription (one device's endpoint), cursor.
- 'email': the test inbox: mail kept unsent (branch with Send email off; preview sends to test addresses like qa+1@example.com) and other preview sends, as text with links (sign-in codes, reset links).