Schematex
sequence·OMG UML 2.5.1·software, infrastructure·complexity 3/3·since v0.5.1

Retry, timeout, and circuit breaker

UML sequence diagram for a gateway calling a payment service through a circuit breaker, with retry attempts, timeout handling, a break fragment for an open breaker, and an asynchronous fallback event.

For the distributed-systems engineer

Open in Playground →
sequence·§
↘ preview
100%
Sequence Diagram — Checkout payment resilience 5 participants, 12 messages, 4 combined fragments. Checkout payment resilience Client Checkout API Circuit Breaker Payment Provider «queue» Fallback Queue break [authorized] alt [response before timeout] [timeout] loop [1,3] alt [breaker closed] [breaker open] 1. POST /checkout/pay 2. allowRequest() 3. permit 4. authorize(amount) 5. auth result 6. 200 Authorized 7. recordFailure(timeout) 8. enqueue retry context 9. 202 Pending verification 10. reject 11. enqueue deferred payment 12. 503 Retry later
UTF-8 · LF · 30 lines · 876 chars✓ parsed·1.4 ms·10.7 KB SVG

Scenario

A checkout API must protect itself from a slow or failing payment provider. The diagram makes the resilience policy reviewable: the gateway checks the breaker, retries bounded attempts, records timeouts, and falls back to asynchronous recovery instead of blocking the customer forever.

Annotation key

Sequence diagram syntax