Failure Modes

The console surfaces the most common engine and config failures as explicit diagnostic banners rather than blank overview cards or silent 500s. Every banner follows the same format so operators always have a predictable next step.

Banner format

Every diagnostic banner contains:

• A short literal headline (e.g. Engine unreachable, Config missing).
• The resolved environment label.
• A Next step pointer — usually a direct link into the Railway dashboard for the affected service or a runbook anchor.
• The raw error string, collapsed behind a disclosure.

Engine unreachable

Raised when the server-side call to the engine fails with a connection-level error. Tells the operator to check the engine's Railway service and links to the operations runbook.

Config missing

Raised when the engine returns 404 for a config section the console expects to exist. Points to the canonical config/ directory and notes which section was requested.

Capability blocked

Raised when /api/v1/runtime/capabilities returns available: false for a capability the page depends on. The reason string from the engine is shown verbatim.

For ops procedures and contact points, see the operations runbook. The docs freshness audit (Task 6) will alert on drift between these failure descriptions and what the console actually renders.

Return to Control Plane Overview.