Race Condition

In plain language

Two actions are using or changing the same thing without enough coordination. Each action may look reasonable by itself, but different interleavings can produce different results.

Why it matters

Race conditions can create intermittent failures that are difficult to reproduce because the same actions may succeed or fail depending on timing.

The same pattern can appear in human workflows when people update shared information from different copies or act before another step is complete.

Example

Two software processes read version 1 of the same record. Each calculates a different update and writes it back. One update overwrites the other.

In a human workflow, two coworkers edit separate copies of the same task list and upload them without reconciling their changes. The final list depends on when and how those updates arrive.

Common misconception

A race condition is not always about which operation finishes first. The more durable idea is that the result depends on relative timing or order. In a last-write-wins example, the final value may be determined by what writes last.