Overview
rave-trading operator control plane. Engine health probe: ok (200, 44ms).
Service Status
Engine unreachable from Staging — capabilities endpoint failed. Dependency:
ENGINE_API_URL (runtime/capabilities). Next step: check Railway service health for the engine, verify ENGINE_API_URL/ENGINE_API_KEY, and consult the engine-unreachable runbook at docs.rave-trading.com/failure-modes.Pricing Health
Pricing health unavailable in Staging — the capabilities endpoint failed, so soft-quote freshness cannot be read. Dependency:
GET /api/v1/runtime/capabilities. Next step: verify the engine is reachable and that the oracle/source upstream is up.Circuit Breaker
Circuit-breaker state is not yet exported by the engine runtime in Staging. See the rave-engine circuit-breaker config and logs for current state.
- docs.rave-trading.com/failure-modes
- Engine runbook:
docs/RUNBOOK.md
Recent Failures
No recent-failures feed available in this build for Staging — surfacing failures is tracked in a follow-up. For now, see the operator/audit page (once Task 3 lands) and the Railway deploy logs linked below.
Market Hours
Market-hours status unavailable in Staging — the
market-closure config could not be loaded. Dependency: GET /api/v1/operator/config/market-closure. Next step: verify the operator API is reachable and that the running engine build has the market-closure config section.Engine Limits
Engine limits unavailable in Staging — the limits endpoint failed. Dependency:
GET /api/v1/limits. Next step: check that the engine is reachable from this environment and that ENGINE_API_URL is configured; otherwise consult the failure-modes runbook.Deployment and Service Links
Surface URLs for Staging: