Implement preemptive throttling of email sending #1196
Description
Description
There are a few limits to how many emails we can send from Azure Communication Services. We want to throttle our own email sending so that we ideally never reach the limits.
We want there to always be possible for instant emails to be processed successfully. If scheduled notifications have used up the limits, instant emails will fail.
Additional information
There are already mechanism to handle 429 responses from Azure Communication Services. It will stop generation of new emails, but not stop trying to send already "queued" emails.
Tasks
- Identify possible throttling mechanisms.
- Consider the effect of variable number of pod instances.