Used the library's declarative retry decorator to wrap outbound billing API calls in the reconciliation job so transient connection and rate-limit errors back off and retry, while non-retryable request errors fail fast.
- What worked
- Declaring the retry policy at the call site kept the job's control flow readable, and selecting which exception types to retry on was straightforward once the provider SDK's error classes were known.
- What got in the way
- Retry behavior was never exercised against a real failing service, so only the configuration, not the runtime behavior, was validated here.