1 Antwort
- Neueste
- Die meisten Stimmen
- Die meisten Kommentare
0
In the meantime I found to approaches by myself:
-
AWS says we should follow this documentation: https://aws.amazon.com/blogs/messaging-and-targeting/how-to-handle-a-throttling-maximum-sending-rate-exceeded-error/
-
SAP says:
- How the System Reacts on Amazon's Throttling
- When Amazon runs into throttling, Amazon returns an error message. The SAP system reacts on it by reducing the send rate and processing the failed messages.
- When Amazon SES runs into throttling, it returns an error message with the following text: API error: Code "400", Reason: "Bad Request", Message: "Throttling Maximum sending rate exceeded."
- This happens if the maximum send rate is exceeded.
- The campaign execution reacts on it by reducing the number of parallel sent request to Amazon SES. Messages that failed due to the Amazon SES error are automatically reprocessed by the campaign execution.
- As result of throttling the campaign execution needs more time to process all requests because it sends less in parallel to avoid that the maximum send rate is exceeded again.
**Recommendation **If the issue still persists, we recommend to exceed the quota at Amazon.
So - no final solution yet, but hopefully one of both will act! I keep you up to date here.
beantwortet vor 2 Jahren
Relevanter Inhalt
- AWS OFFICIALAktualisiert vor 2 Jahren
- AWS OFFICIALAktualisiert vor einem Jahr
- AWS OFFICIALAktualisiert vor 2 Jahren