Alaister YoungandAlaister Young 16bd06dfb8 fix(studio): silence status page errors when incident.io isn't configured (#51315) ...

Running Studio locally without the incident.io env vars produces a 500
from `/api/status-page` on every fetch, plus a server-side log and a
client `console.error`. Retries and the 5-minute refetch keep repeating
them, so the dev console stays noisy.

**Changed:**
- `lib/api/status-page.ts` – when `INCIDENT_IO_WIDGET_URL` is unset
outside production, return an empty (degraded, short-cached) status page
instead of throwing. The missing API key / status page ID log is also
limited to production. Production behavior is unchanged.
- `data/platform/status-page-query.ts` – remove the client-side
`console.error`, which repeated the error that React Query already
exposes

**Added:**
- Tests for the missing widget URL in dev (empty payload, no error log)
and in production (still throws)

## To test

- Run Studio locally in platform mode without `INCIDENT_IO_*` set: no
status page errors in the terminal or the browser console, and
`/api/status-page` returns 200 with empty arrays
- Support form and project creation still render normally (no status
banner, status page link points to status.supabase.com)

Co-authored-by: Alaister Young <10985857+alaister@users.noreply.github.com>

2026-10-07 14:58:43 +02:00

..

incident-banner-query.ts

Revert "fix: Disable/incident-banner query" (#43933)

2026-03-19 12:32:48 -04:00

incident-status-query.ts

cleanup: fix import order and prefixes for studio/data (#44501)

2026-04-03 09:15:57 +02:00

incident-status-utils.ts

cleanup: fix import order and prefixes for studio/data (#44501)

2026-04-03 09:15:57 +02:00

keys.ts

feat(studio): status page client data layer + support form (#50984)

2026-09-29 07:53:28 -04:00

status-page-query.ts

fix(studio): silence status page errors when incident.io isn't configured (#51315)

2026-10-07 14:58:43 +02:00