The bill for retrying a failed email API call includes submission attempts, worker capacity, retained evidence, and the investigation required when an outcome remains ambiguous. For a healthtech compliance notice, the dominant storage term can be repeated message bodies: under an illustrative workload of 10,000 notices, four retained attempt snapshots per notice, and a 100 KB body, those snapshots occupy 4 GB before indexes or replication. Keeping one body per notice reduces that component to 1 GB; attempt metadata remains additional. These are design assumptions, not measured traffic or prices.
Short answer: use capped exponential backoff with jitter for failures that the API contract identifies as transient, honor applicable retry instructions, and preserve a stable notice identity across attempts. Bound retries by both an attempt budget and a notice deadline. When submission may already have succeeded, reconcile the outcome or use documented idempotency support before sending again.…