# 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… - Source: https://docs.ghlcustomercare.com/docs/workflows/workflow-builder/troubleshooting-workflow-executions-race-conditions - Section: Workflows / Workflow Builder - Reading time: 1 min - Images: 5, each explained below - Modified on Mon, 2 Feb at 10:44 AM --- 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** - [Open the exact execution via the message deep link](#open-the-exact-execution-via-the-message-deep-link)[](#example-race-condition-add-tag-executed-but-not-added) - [Example Race Condition: Add Tag Executed But Not Added](#example-race-condition-add-tag-executed-but-not-added)[](#how-to-prevent-a-race-condition) - [How To Prevent a Race Condition](#how-to-prevent-a-race-condition) --- ## **Open the exact execution via the message deep link ** 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)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/48237097817/original/pPEyoJgImK3T2gGbzJKB67cfk97rECsmrQ.png) **Example Race Condition: Add Tag Executed But Not Added (image 1 of 5)** 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. - What this covers: In this example, we can see that the tag was added successfully to this contact in the workflow execution logs. - Next: However, 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)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/48237098616/original/QV-c-v9lQ1vmsqrWFtQJxnTd9FnvBUttZQ.png) **Example Race Condition: Add Tag Executed But Not Added (image 2 of 5)** 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. - What this covers: However, when we check the contact record, there is no sign of the tag. - Next: 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. 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)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/48237097905/original/PtKVYprrQGKLzBww-ZXcYyVETqRuSFn5pg.png) **Example Race Condition: Add Tag Executed But Not Added (image 3 of 5)** 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. - What this covers: 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. - Next: To 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](https://www.loom.com/share/f4adf9e14dab429da0cc2fedbb7e5e36) ![How To Prevent a Race Condition (image 4 of 5)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155037771738/original/aZsqCC0OAIfQkSQqUbLor31c9DWXbFaYeg.png) **How To Prevent a Race Condition (image 4 of 5)** 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. - What this covers: https://www.loom.com/share/f4adf9e14dab429da0cc2fedbb7e5e36 - Next: With 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)](https://s3.amazonaws.com/cdn.freshdesk.com/data/helpdesk/attachments/production/155037771768/original/dfxKTUGbzhTGDHHNdPEUqtvKhpVqmyF86A.png) **How To Prevent a Race Condition (image 5 of 5)** 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. - What this covers: With a Wait 1 minute action, there is no chance of the race condition occurring. --- Documentation for GHL Customer Care. Support: support@ghlcustomercare.com