Understanding and Preventing Race Conditions
Race conditions occur when two servers attempt to update the status of a contact at nearly the same time. Race conditions commonly occur due to several factors, including multiple triggers being set for the same action, actions being executed simultaneously for a contact, or similar timing of executions within automation for the same contact. These scenarios can cause conflicts or unpredictable behaviour in workflows, as the system may attempt to process overlapping actions at the same time, leading to unintended outcomes.
Examples:
Utilizing both the Appointment Status and Customer Booked Appointment triggers for identical functions can create conflicts.
Simultaneous firing of opportunity changes and appointment triggers within the same workflow.
Adding a contact tag at the same time across multiple workflows.
Identifying Race Conditions
To determine if you're experiencing a race condition, investigate the workflow execution history/status and timing. Look for:
Duplicate messages.
Workflow history indicating a different trigger than intended.
Tags are being added without reflecting in the contact.
Unexpected behavior due to similar timing in triggers.
Preventing Race Conditions
Implementing the following strategies can help prevent race conditions:
Add a Wait Step
Insert a 2-minute wait step before actions that might be affected by race conditions. This allows the system to process actions correctly.
Use Distinct Triggers
Avoid using the same or similar triggers for the same actions across workflows.
Be Specific with Filters
Tailor your filters to the specific actions a lead might take, reducing the chance of simultaneous trigger firing.
Pass Input Trigger Parameters
When adding a contact to another workflow, use the "Pass Input Trigger Parameters" option with the "Add To Workflow" action to ensure data is passed correctly.
Troubleshooting Tips and Best Practices
If you encounter unexpected behaviour, follow these troubleshooting steps:
Check Enrolment History and Execution Logs: This can provide insights into timing and trigger issues.
Investigate Multiple Workflows: Look for workflows that may fire at the same time due to customer actions.
Use Unique Trigger-to-Action Implementations: Avoid using multiple workflows for the same actions.