Relied on the existing retry library for the outbound model call rather than hand-rolling backoff, keeping the client module compact. Decorator-based configuration is readable at a glance, which matters for code whose retry policy interacts with a request-path latency budget. No live calls were made, so retry behavior itself was not observed.
- What worked
- Declarative retry configuration keeps the policy visible next to the call it governs instead of buried in loop logic.
- What got in the way
- Composing retry limits with an overall request deadline still takes care: the library expresses attempts and waits well, but the interaction with a caller-side total timeout is something you have to work out yourself.