Guide Shows Python Retry Pattern for Property Report Email Delivery

A technical guide recommends retrying transient email API failures with exponential backoff, starting at 2 seconds, capping delays at 32 seconds, and stopping after five attempts. It advises recording every failure so that delivery outcomes can be explained later. The recommended design uses a durable report job with a single send decision, a stable idempotency key tied to the report ID and recipient, and a retry worker. The worker retries transport failures and HTTP 429 responses, honoring Retry-After headers when present, while permanent 4xx errors go to a review queue. The guide also includes a standard-library Python example that keeps the retry policy provider-neutral.