React & Modern Frontend (445 Qs)•Part 10: Modern React 18, React 19 & Next.js Patterns (317 - 353)
How do you handle race conditions in Redux?
A race condition happens when multiple async requests are in flight and they resolve out of order — e.g., a user types quickly in a search box, an older request for "re" resolves after the newer request for "react", overwriting the correct results with stale ones.
createAsyncThunk+ request tracking: store the latestrequestIdand ignore results from stale requests.
javascript
const fetchResults = createAsyncThunk("search/fetch", async (query) => {
const res = await fetch(`/api/search?q=${query}`);
return res.json();
});
builder.addCase(fetchResults.fulfilled, (state, action) => {
// Only apply the result if it belongs to the most recent request
if (action.meta.requestId === state.currentRequestId) {
state.results = action.payload;
}
});
- Abort stale requests using
AbortController, whichcreateAsyncThunksupports viathunkAPI.signal— cancel the previous request when a new one starts. - Debounce/throttle the trigger (e.g., debounce keystrokes) so fewer overlapping requests are made in the first place.
- Use RTK Query, which automatically de-duplicates in-flight requests, cancels/ignores stale ones, and keeps the cache consistent without manual bookkeeping.