Skip to content
Workflows

Troubleshooting Workflow Executions - Race Conditions

A Race Condition is when two (or more) updates happen at the same time (in the same second). The two changes "race" and they might execute in a different…

1 min read294 words5 explained imagesUpdated Mon, 2 Feb at 10:44 AM
View as markdownOpen in ClaudeOpen in ChatGPT
Each image has a one line explanation. Switch to full detail for the step it belongs to, the fields and buttons involved, examples and the whole procedure.
On this page
  1. Open the exact execution via the message deep link
  2. Example Race Condition: Add Tag Executed But Not Added
  3. How To Prevent a Race Condition

A Race Condition is when two (or more) updates happen at the same time (in the same second). The two changes "race" and they might execute in a different order than they should, or one might signal that it executed but it really didn't.


TABLE OF CONTENTS


Opening the execution directly from the impacted message ensures you’re reviewing the correct run, contact, and timestamp before diagnosing timing issues.

Steps:

  1. Go to Conversations and open the conversation with the impacted message.

  2. Open message details for the message.

  3. Click Workflow (deep link) to open Execution Details with context loaded.

  4. Review the timestamps and action order to confirm whether multiple actions fired in the same second.

Fallback:
If the Workflow link is not available in message details, open the execution from logs:

  • Workflows → open workflow → Logs, then filter/search by contact and the time window around the message.


Example Race Condition: Add Tag Executed But Not Added

In this example, we can see that the tag was added successfully to this contact in the workflow execution logs.

Example Race Condition: Add Tag Executed But Not Added (image 1 of 5) What this shows In this example, we can see that the tag was added successfully to this contact in the workflow execution logs. What this shows Illustrates the "Example Race Condition: Add Tag Executed But Not Added" section of "Troubleshooting Workflow Executions - Race Conditions". This screenshot appears in the "Example Race Condition: Add Tag Executed But Not Added" section of "Troubleshooting Workflow Executions - Race Conditions". The text alongside this image reads: In this example, we can see that the tag was added successfully to this contact in the workflow execution logs. Immediately after, the guide continues: However, when we check the contact record, there is no sign of the tag. Image 1 of 5 What this coversIn this example, we can see that the tag was added successfully to this contact in the workflow execution logs. Next stepHowever, when we check the contact record, there is no sign of the tag.

However, when we check the contact record, there is no sign of the tag.

Example Race Condition: Add Tag Executed But Not Added (image 2 of 5) What this shows However, when we check the contact record, there is no sign of the tag. What this shows Illustrates the "Example Race Condition: Add Tag Executed But Not Added" section of "Troubleshooting Workflow Executions - Race Conditions". This screenshot appears in the "Example Race Condition: Add Tag Executed But Not Added" section of "Troubleshooting Workflow Executions - Race Conditions". The text alongside this image reads: However, when we check the contact record, there is no sign of the tag. Immediately after, the guide continues: Lets go back to the execution log and pay attention to the time. The "Add to workflow" and "Add Tag" action fired at the same time within the exact same second, which is a race condition. Image 2 of 5 What this coversHowever, when we check the contact record, there is no sign of the tag. Next stepLets go back to the execution log and pay attention to the time. The "Add to workflow" and "Add Tag" action fired at the same time within the exact same second, which is a race condition.

Lets go back to the execution log and pay attention to the time. The "Add to workflow" and "Add Tag" action fired at the same time within the exact same second, which is a race condition.

Example Race Condition: Add Tag Executed But Not Added (image 3 of 5) What this shows Lets go back to the execution log and pay attention to the time. What this shows Illustrates the "Example Race Condition: Add Tag Executed But Not Added" section of "Troubleshooting Workflow Executions - Race Conditions". This screenshot appears in the "Example Race Condition: Add Tag Executed But Not Added" section of "Troubleshooting Workflow Executions - Race Conditions". The text alongside this image reads: Lets go back to the execution log and pay attention to the time. The "Add to workflow" and "Add Tag" action fired at the same time within the exact same second, which is a race condition. Immediately after, the guide continues: To fix the race condition, just add a Wait action of 1 minute. Image 3 of 5 What this coversLets go back to the execution log and pay attention to the time. The "Add to workflow" and "Add Tag" action fired at the same time within the exact same second, which is a race condition. Next stepTo fix the race condition, just add a Wait action of 1 minute.

How To Prevent a Race Condition

To fix the race condition, just add a Wait action of 1 minute. 

https://www.loom.com/share/f4adf9e14dab429da0cc2fedbb7e5e36

How To Prevent a Race Condition (image 4 of 5) What this shows https://www.loom.com/share/f4adf9e14dab429da0cc2fedbb7e5e36 What this shows Illustrates the "How To Prevent a Race Condition" section of "Troubleshooting Workflow Executions - Race Conditions". This screenshot appears in the "How To Prevent a Race Condition" section of "Troubleshooting Workflow Executions - Race Conditions". The text alongside this image reads: https://www.loom.com/share/f4adf9e14dab429da0cc2fedbb7e5e36. Immediately after, the guide continues: With a Wait 1 minute action, there is no chance of the race condition occurring. Image 4 of 5 What this covershttps://www.loom.com/share/f4adf9e14dab429da0cc2fedbb7e5e36 Next stepWith a Wait 1 minute action, there is no chance of the race condition occurring.

With a Wait 1 minute action, there is no chance of the race condition occurring.

How To Prevent a Race Condition (image 5 of 5) What this shows With a Wait 1 minute action, there is no chance of the race condition occurring. What this shows Illustrates the "How To Prevent a Race Condition" section of "Troubleshooting Workflow Executions - Race Conditions". This screenshot appears in the "How To Prevent a Race Condition" section of "Troubleshooting Workflow Executions - Race Conditions". The text alongside this image reads: With a Wait 1 minute action, there is no chance of the race condition occurring. Image 5 of 5 What this coversWith a Wait 1 minute action, there is no chance of the race condition occurring.

Was this guide helpful?

Related guides