Automation evaluated as False although the conditions are Matching

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 triggered. Subsequently, the lead got merged with another lead, and the opportunity association changed. However, in the automation's trigger data, we have the older Lead ID, causing the evaluation to follow the False path instead of the expected True path.

Steps to Resolve:
  1. Identify the Trigger Data: Check the automation's trigger data to identify the Lead ID being used.
  2. Verify Lead Association: Confirm the current lead association for the opportunity.
  3. Re-trigger Automation: Manually re-trigger the automation on the updated Lead ID to ensure it evaluates correctly.
  4. Monitor and Validate: Monitor the automation to ensure it follows the correct path and validate the results.
Preventive Measures:
  1. Implement checks in the automation to handle lead mergers and changes in lead associations.
  2. Instead of using Evaluate on Trigger data in the automation card, Evaluate on Latest data can be Used (This is Case Sensitive)

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

    • Lead assigned more than lead assignment quota

      Issue Hi Team you can face some issue where lead assignment quota is enabled that Leads are assigned to users more than the lead assignment quota via automation. Reason for this is that the lead assignment quota is only calculated for lead distribute ...

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

    • Date format is showing as yyyy-mm-dd where mail merge is used

      Issue reported: The Company profile employs a distinct date format, yet the mail merge displays dates in the yyyy-mm-dd format. Solution: This is the default behavior of the system since the values are stored in the backend database in the format ...

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