Hi,
The action in the automation is to add an email to the queue. Once added the email will be send the next time your cron is triggered. Hence, your delay.
Essentially your cron task is triggered by our cron server. You have enabled this in your configuration on the license tab. (Enable automatic tasks). The minimum interval for the our cron service is 15 minutes.
In your configuration you have configured to send one batch every 6 minutes. This does not match the minimum time interval of our cron service. As a result something called web cron will kick in. This is a meganism in your Acymailing that will trigger the cron task when someone visits your site. But if no one is visiting your site the web cron will not be triggered, so you can't rely on it.
As an alternative you can setup a cron task on your own server or any give cron service provider. You'll find the cron url on the license tab in your Acymailing configuration.
In case you decide to use your own cron service there are some things to keep in mind.
- Disable the automatic tasks on the license tab in the Acymailing configuration. This will stop our cron service triggering your Acymailing. This way you prevent cron tasks running in parallel, which would slow down your sending.
- Make sure the time interval in the queue process matches the time interval you use on your cron service
- Make sure the number of emails per batch can be send within the given timeframe.
- You probably also have to lower the size of the batch to prevent exceeding your maximum sending limit at your host or smtp service provider.