CRON Automation Not triggered even after ALL condition is True

Hi Team,

You may encounter an issue where CRON-type automation (Mostly regular interval type trigger) will not trigger even if all the inclusion criteria is satisfied.

Reason for that will be that there is a certain limit in Regular interval also for each interval type trigger. For example it can be a Daily trigger at some time or Monthly or Weekly. 

Steps to Debug

1. First check the inclusion criteria and use the same filters in Advanced Search. 
   
2. If the count is increasing the allowed limit in Advanced search result then Automation will not trigger on any of the Lead. (You can check the limit with any automation team spoc)
   

For example for one of my account count in advanced search was 2,28,238 Leads. However the allowed limits were as below:-

{ "HourlyLimit": 2500, "DailyLimit": 100000, "WeeklyLimit": 25000, "MonthlyLimit": 25000, "UserHourlyLimit": 5000, "UserDailyLimit": 25000, "UserWeeklyLimit": 25000, "UserMonthlyLimit": 25000 }

So Automation did not triggger on any of the Lead.

Thanks,

Akash

• Related Articles

• If/Else condition returning false positive | Automation card error

  Issue Reported: The If/Else card within the automation was generating false positives for multiple leads, causing these leads to proceed through the automation incorrectly. If/ Else card condition: Activity of the lead is ..... and ..... Solution: ...

• Automation not trigger on owner/Lead update

  Hi Team, You may encounter an issue where Automation has not triggered on Lead update, where the field will be owner update. Reason To Debug this please check the owner update is done by which card/method. If Owner has been updated by "Lead ...

• Automation evaluated as False although the conditions are Matching

  Issue Statement: Although the lead/opportunity is satisfying the condition set in the automation, the automation has evaluated as False. Root Cause Analysis (RCA): The opportunity was associated with a different lead when the automation was ...

• CFS field to be added in the trigger for automation.

  Issue: CFS field to be added to the trigger for automation. Explanation: If we want to add a CFS field in the trigger card as a trigger condition or trigger field, then we can achieve this by enabling the setting from the backend by raising CM. ...

• Restrictions on adding sub-automation in Automation(Lead Type Trigger)

  Product behaviour: Sub-Automations created for an Activity type Trigger cannot be used in other automations with Lead type Triggers. Root cause: Sub-automation cards for Lead Type Triggers have a validation that only allows Sub-automations created ...