If too many communications are sent to the same recipient(s) within a short period, Agillic assumes the send out has been misconfigured and initiates a system pause. This pauses all send-outs, including email and SMS.
In this article, you will find information about;
- When Does the Production Environment Pause?
- Where Can I See if my Agillic Production Environment is Paused?
- How to Handle a System Pause?
- How to Resume After a System Pause?
- How to Get Notified if your System Pauses?
- What Happens to Flows That are Being Scheduled or Triggered When the System is Paused?
When Does the Production Environment Pause?
All Agillic Production Environments can end up pausing under specific circumstances. By default, these circumstances are if:
- A single recipient has received more than 10 communications in less than 10 minutes.
- 3 recipients have received 5 communications within 10 minutes.
It's possible to change the default limit if you need to. To do this, submit a request to our Product Specialists in Support.
Where Can I See if my Agillic Production Environment is Paused?
When Production pauses, you will receive an email if you've registered email addresses in the Alerts Section in the Settings Module.
You can also see if your Production Environment has been paused in the Flows widget when you log in to either your Staging or Production environment. It's also visible in the Settings module in the Alerts section.
An example of what a paused system looks like in the Flows widget on the start page
An example of what a paused system looks like in the Settings module
How to Handle a System Pause?
To fix a system pause, you'll need to stop the faulty send out. It's important to investigate why the pause happened to prevent a system pause occurring again. You can investigate in a number of ways:
- Investigate recipients with the given email address or mobile number to find the Flow(s) with the faulty send out. In the email you receive, we list the AGILLIC_ID of recipients who caused the pause.
- Pause the Flow(s) with the faulty send out.
- Deactivate the Flow(s) with the faulty send out.
- Identify and fix the underlying challenge that has caused too many communications to one or more recipients within the defined time period.
Once you've fixed the underlying cause of the system pause, you can resume send-outs using the below steps.
How to Resume After a System Pause?
Once you've fixed the source of the system pause, you can resume the paused system and start sending out communications again.
- Log in to Production.
- Open the Settings module.
- Under the 'System Settings' section in the left sidebar, select 'Alerts'. If the system has been paused, a 'Resume' button will be visible.
- Click on the 'Resume' button.
Your instance will now resume its send-outs. It can take up to 30 minutes before recipients who were still in the middle of a Flow to receive communications again.
How to Get Notified if your System Pauses?
We strongly advise that you register email addresses so you'll be notified if the system pauses. To get notified if your system pauses, you should:
- Log in to Production.
- Open the Settings module.
- Under the 'System Settings' section in the left sidebar, select 'Alerts'.
- Fill in one or more email addresses. You can use a comma to separate email addresses if you want to insert more than one.
- Click 'Save'.
The filled-in email addresses will now receive emails in case your Production environment pauses. The email will contain IDs for the recipients which caused the system to pause.
3 email addresses set up to receive emails if the Production environment pauses
What Happens to Flows That are Being Scheduled or Triggered When the System is Paused?
You may be in a situation where you have scheduled or triggered Flows while the system is paused. You may want to review this to ensure that send-outs have actually continued after the system is resumed.
Scheduled Flow During System Pause
If a Flow was scheduled to execute whilst the system was paused, Agillic will re-attempt to execute it once the system resumes.
When Agillic executes the scheduled Flow after the system resumes, it will evaluate the Conditions based on that present moment after the system is resumed. This ensures that crucial Conditions, such as permissions, will still be evaluated for queued Flows. It also means that if you have time-based Conditions, recipients aren't sent communications that are no longer valid for them as the time has passed.
Triggered Flow During System Pause
If Flows are triggered while the system is paused, Agillic will store these executions and simply start them when the system is resumed. Since triggered Flows do not evaluate Target Group Conditions, you're less likely to be facing the same issues as with scheduled Flows.