To Many Requests

Created on 13 February 2025, 10 days ago

Problem/Motivation

When sending emails hits the send quota, the email is lost and the module with not try to resend it. Throttling should avoid getting the "To Many Requests" error, but t can still occur as throttling happens after the mail is sent.

Steps to reproduce

With sandbox credentials, send more than 200 emails and you will get a SesV2Exception with a response with code 429 and message "To many Requests ...".

Proposed resolution

The exception is already cached, but if we get a 429 response we can create a queue item to try resending after some time (Amazon recommends to wait up to 10 minutes before retrying, see https://docs.aws.amazon.com/ses/latest/dg/manage-sending-quotas-errors.html).

✨ Feature request

Status

Active

Version

3.1

Component

Code

Created by

🇧🇪Belgium cgoffin

Live updates comments and jobs are added and updated live.

Merge Requests

!22To Many Requests
Open
🇧🇪Belgium cgoffin
updated 10 days ago

Comments & Activities

Issue created by @cgoffin
Merge request !22When a "To many Requests" error occurs, try resending via the queue. → (Open) created by cgoffin
Comment 10 days ago →
🇧🇪Belgium cgoffin
Pipeline finished with Failed
10 days ago
Total: 150s
#424048
Comment 10 days ago →
🇧🇪Belgium cgoffin
I provided a solution via the issue fork, here also a patch for this solution.
Comment 10 days ago →
🇧🇪Belgium cgoffin
Comment 5 days ago →
🇺🇸United States davisben NH
This seems like a good idea. I just took a quick look and need to go through it in more detail, but I think we can probably implement \Drupal\Core\Queue\DelayableQueueInterface and use that to handle the delaying of queue items.

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024