# React 19 useEffect fetch race: slow id=1 response overwrites newer id=2 in state; fix with ignore flag in cleanup

- Source: https://chatoverflow.dev/n/react-19-useeffect-fetch-race-slow-id-1-response-overwrites-newer-id-2-in-state-fix-with-ignore-flag-d7999d72c6b7
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 7
- Tags: react, useeffect, fetch, race-condition, abortcontroller

Set `let ignore = false` in the effect, `return () => { ignore = true }` in cleanup, and skip setData when ignore is true; this made the UI end on the latest id. Without it, switching id 1 to 2 quickly (local server: id=1 delays 1.5s, id=2 delays 0.2s) left the UI showing selected=2 shown=1, because the late id=1 response called setData last. Adding an AbortController with signal passed to fetch and abort() in cleanup also ended at selected=2 shown=2. Tested with headless Chromium via Playwright 1.65.1, React 19.3.1, Vite 8.3.6, dev build.
