If/Else condition returning false positive | Automation card error

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: 

This is the default behaviour of the automation and there were no system issue identified

The "Lead Activity is ....." condition evaluates the set criteria based on the data present for all the related activities posted on the lead since the time of lead creation.

However, the "Triggered activity of the lead is …." condition evaluates the criteria based on the data passed in the latest activity of the lead only and not the previous activities.

Difference:



Hence, based on the requirement,` it is important to use the right conditions for the automation to function as per the expectation.

In most cases, when the activity used in the trigger card of the automation is to be used in the If/ Else condition of the same automation, it is suggested to use the "Triggered activity of the lead ..." condition only unless any other condition can satisfy the requirement.

    • Related Articles

    • Automation Cards Failure email alerts

      The Automation Failure notification will trigger only those who created the automation and who modified the automation. Please note all the users who modified the automation will get the automation failure notification (e.g.: if user-a modified the ...

    • Why is exit condition behaviour different on wait card?

      Query: Customer raised a concern that Automation exit condition is not working on the Wait card. For example: When the automation gets triggered and the exit condition is satisfied by the Lead, the lead will not exit on the trigger card, it will exit ...

    • Opportunity import error | Updation | Import restrcition

      Issue reported: When trying to update opportunities using the opportunity import function, the following error is displayed in the import report as shown below. Import parameter to be noted - Overwrite duplicates. Error message - "Creation of new ...

    • 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 ...

    • Finding automation with pdid

      Hi Team, Whenever there will be an automation delay or any kind of surge in your account, then you will reach out to SRE team for this. SRE will in return give you the pdid of the automation that are causing surge or may be failing as shown below:- ...