Operational disclosure

runtime-degraded-without-env

Tenant scope

hybrid dependency

Routes stay reachable but disclose when tenant, provider, or env dependencies are missing.

Diagnostics

Runtime connectivity health for your Settler workspace. All checks source from live API calls — no synthetic values.

Connectivity checks failed

UNKNOWN

Connectivity checks

Live checks run on each page load against your configured environment.

Environment variables

Required Supabase and app environment variables are present.

Error

Database (Prisma/PostgreSQL)

Prisma can reach the configured database endpoint.

Unknown

Supabase connectivity

Supabase client can reach the configured project.

Unknown

Runtime environment

App runtime can read its required configuration.

Error

Scope of these checks: connectivity checks validate that the app can reach its core dependencies. They do not surface application-layer metrics (CPU, memory, queue depth) — those are available in your infrastructure provider console.

Worker-level metrics, cache state, and fleet telemetry are not exposed here because this deployment model does not provide application-layer resource visibility via the web runtime. If you need infrastructure observability, consult your Vercel / host dashboard.

Operator surfaces

Evidence-backed observability surfaces with query-backed truth.

Operator digest Run history Tenant observability

Governance controls

Public status page

Audit trail

Support & reporting

Report an issue Support inbox (admin)