Automation conditions play a crucial role in ensuring workflows execute as expected in Rocketlane. One commonly used condition, 'is exactly,' has specific limitations that can cause automations to behave unexpectedly if the condition is not configured correctly.

Key Limitations of the 'Is Exactly' Condition

The 'is exactly' condition functions effectively only under certain circumstances, which depend on the field type and the number of values selected:

1. Multi-Select Fields - The 'is exactly' condition fails if multiple values are selected in fields such as single select fields configured to allow multiple options. For instance, if a field contains multiple entries like 'Paypal' and 'Stripe,' the automation will not trigger as expected. In these cases, you should use the 'is one of' condition instead to enable automation for multiple values.

2. Single Select Fields with One Value - The 'is exactly' condition works correctly when a single select field has only one value. For example, if only 'Paypal' is selected, the condition will trigger the automation as expected. The issue arises only with multiple values.

3. Boolean Fields - There is no compatibility issue with boolean fields (fields with true/false options). Automations using the 'is exactly' condition in these fields will work as intended.

Troubleshooting and Best Practices for Automation Conditions

If you encounter issues with the 'is exactly' condition, consider the following troubleshooting tips and best practices:

1. Replace 'Is Exactly' with 'Is One Of' - Whenever the field in question may include multiple values and the automation fails to trigger, changing the condition from 'is exactly' to 'is one of' will allow the automation to account for multiple selections. This is especially useful for fields like a multi-select dropdown.

2. Structuring Automations for Status Changes - For scenarios where using 'is one of' introduces an either/or dynamic and the automation needs to act on status changes, set up two separate action blocks with identical triggers but different conditions. By adding each condition separately, you ensure that the automation triggers correctly regardless of the specific status change.

Example Scenarios

To help illustrate these principles, consider the following examples:

1. Multi-Select Field Automation - Problem: A marketing project’s payment method field includes both 'Paypal' and 'Stripe,' but the automation doesn’t trigger. - Solution: Change the condition to 'is one of' and list the accepted values ('Paypal' and 'Stripe') in the configuration.

2. Single Value Field Automation - Context: An approval field uses a single select dropdown with 'Approved' as the only value. - Result: The 'is exactly' condition will trigger the automation whenever the field is set to 'Approved.'

3. Status Changes - Challenge: Automating updates when a project status changes from 'In Progress' to 'Completed.' - Solution: Create two duplicate action blocks, each targeted to one specific status change condition. This ensures precise triggering of the automation for either case.