Visibility into Queue
Would be great to access and manipulate messages that are currently in the queue. Perhaps with the ability to purge based on recipient domain.
Thanks for submitting and supporting this feature suggestion!
Back near the end of July 2018 our product team introduced a solution based on this idea. You can now clear all scheduled and unsent messages in a domain’s queue. To do so:
1. Login to your Mailgun account.
2. Select the “Domains” section of the control panel.
3. Select the dropdown arrow next to “Clear Domain Queue.”
4. This will permanently delete all scheduled and undelivered messages from your queue. Be aware that there is no way to retrieve that data once cleared.
Please keep in mind that we have not built the functionality to delete individual messages from the queue. That is not on our immediate product roadmap but would be a nice feature for our control panel.
In the meantime, please continue to share your ideas and feature requests so we can continue to improve our product for you!
-The MG Team
Any progress on this?
I send an email when a user clicks a button, I only launched yesterday which revealed a bug to me.
A user can press the button several times before the next page loads and now I have several queued messages which will be sent up to 5 times for a single user.
It would be nice to be able to delete queued messages so I can remove the extra ones manually from inside the mailgun dashboard.
Obviously I have fixed my bug but as a new user to mailgun this flexibility could help others when they first turn the service on.
Anton Melser commented
Queue visibility is easy enough to have yourself - Accepted - (Delivered + Failed(severity=Permanent))
Willy T. Koch commented
If I've sent an email to 150 recipients to the mailgun servers and used BatchMessage and setDeliveryTime() to schedule it for the next day at 7 AM, there's currently no way to cancel this message if I decide later, before the set time, to cancel the job.
This could be fixed by getting a return hash value when using finalize() which then could be used with a new function deleteMessageQueue(return hash value) that will cancel the job.
The canceled message still counts the email credits used, of course.
Willy T. Koch
Also an API call to get the number of messages in the queue, so you know when you can batch send without running into the 500k.
We are working on that.