There are several automation tasks for which a 5 minute wait is problematic. As an example, "Unsuspend Services". A customer makes a payment to a late invoice, and their service is waiting for the cron to be unsuspended. Meanwhile they open an emergency ticket, only to have their service unsuspended seconds later. Everyone's time is wasted, and the customer is frustrated.

We set up the cron job to run every 5 minutes, and this is what we recommend. However, for some tasks we should allow them to be run every minute. This would involve at least 2 things:

1. Setting up the cron to run every minute, rather than every 5 minutes. We can recommend 5, but it must be set to 1 minute for intervals of 1 minute to work.
2. For specific tasks, allow an interval of 1 minute to be set.

Which tasks?

• Process Service Changes
• Process Service Renewals
• Provision Paid Pending Services
• Unsuspend Services

For these tasks, add a new interval of 1, prior to 5. 5 should remain the default.

If any tasks are set to 1 minute, and the cron has been running but not running every minute (Check last few runs), display an information/warning box on the top of the Settings > System > Automation page to say:

There are automation tasks set to run every minute, but your cron does not appear to be running every minute. Update your cron to run every minute to take advantage of these shorter intervals.

There may be something else that prevents any cron runs from happening more often than 5 minutes, if so that will need to be adjusted.