Why is exit condition behaviour different on wait card?

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 after the Wait card.

Explanation: This is an expected behaviour of the system, when a wait card is placed between the trigger cards i.e: 'New Activity. and action card (i.e: lead update, Activity update, etc). This happens because the exit condition is evaluated on action cards and 'Wait' card is not an action card hence the exit condition will be completed after the wait card is completed and the Automation reaches an action card.

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

    • Behaviour of Custom filters in Dashlet

      Query: Client can raise concern wherein they would highlight the point that whenever they change the dashlet's filter and refresh it, it goes back to the default filter which means that whenever the client changes the filter to "Lead Stage" and ...

    • Behaviour of Origin field for opportunity created via Import

      Issue: When checked under manage opportunity page the origin field value is empty Root cause: The origin field value is blank, in the scenario where opportunity has been created by Opportunity Import. Solution: As a workaround it is suggested that ...

    • Task owner in opportunity page and in manage task page can be different

      Hi Team, There can be a possibility where the task owner in opportunity page and in manage task page can be different. Reason for this issue:- If the the user Name, Email and phone number everything will be changed for any user who is task owner, ...

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