Fallback & recovery
Bounded retries, per-category failover and 207 Multi-Status resilience.
On this page 3 sections
#Execution and fallback
internal/reliability/executor.go enforces per-provider bulkheads, circuit breakers and bounded retries. Fallback is attempted only among eligible providers for that specific location and data category. Schema validation, stale observation timestamps (>2h old), or coordinate drift violations (>25–50 km) automatically participate in fallback.
#Partial availability in /v1/datasets
When a client requests multiple categories via GET /v1/datasets?datasets=weather,forecast,astronomy, a failure in one category never discards successful categories. The gateway returns 207 Multi-Status with meta.partial=true, delivering all normalized datasets in data alongside structured per-category diagnostics in errors.
#Observability
Use /health, /readiness, /liveness (which bypass client rate-limit buckets so probes remain accurate under load) and loopback-protected /metrics alongside correlated request/trace identifiers to troubleshoot.
docs/openapi.yaml (lean_v1) and docs/openapi.experimental.yaml · Verify against your build before production use.