ATAPI Twin
Pages

Build

Scenarios and faults

Switch the whole twin to Normal, Degraded, or Outage.

The scenario buttons sit on the twin. Normal serves the routes. Outage returns 503 and does not write state. Degraded uses the Faults tab: extra latency, jitter, and a chance of the configured error status and body.

Faults also hold a requests-per-minute limit. 0 means no twin-wide limit. If that twin limit is set, it is the one that counts. Otherwise a route's own limit counts, and an OpenAI route falls back to the model limit on the same tab. Past the limit the call is 429. A chat or models path uses the OpenAI error shape.

A single route can also wait up to 5 seconds via its delay field. That delay is fixed. The fault latency is the one that varies when Degraded is on.

CI sets the scenario with POST /api/v1/twins/{slug}/scenario and {"scenario":"default"}, "degraded", or "outage".