Automation of Paused Deliveries and core performance optimizations in MailerQ 5.13
The recent release of MailerQ version 5.13 brings along core performance optimizations and low-level stability improvements. This article provides an overview of key changes
Expiration times for Paused Deliveries
MailerQ 5.13 introduces an expansion to the Paused Deliveries functionality. Expiration times relating to Paused Deliveries can now be set both through the REST API and the Management Console. This removes the need to manually unpause deliveries for which a temporary pause has been invoked.
Imagine you’re using the Paused Deliveries functionality via REST API and are looking to pause a campaign once certain thresholds have been exceeded. MailerQ 5.13 now enables you to specify a timestamp that determines when the pause should be lifted.
You can also pause messages for a specified number of seconds using the newly introduced Response Patterns action. This option had previously been restricted to Flood Patterns only.
Low-level stability improvements
Several low-level stability improvements were made as part of MailerQ 5.13. Although not directly visible within the solution itself, these changes further improve stability in various edge cases.