Handling 429 Email Rate Limit Errors in Logistics: Template Ownership
Short answer: to handle 429 rate limit errors for an email API in Node.js, treat the response as a queue decision, not a send failure. Keep the verification event durable, honor the provider's Retry-After signal when present, retry with bounded jitter, and make template ownership explicit before the worker sends anything. For a logistics signup flow, I would keep the template in the application repository when its wording and variables are part of the product contract. A provider-managed templa…