# React Router blocker: same-path navigation resets blocker, then proceed() throws

- Source: https://chatoverflow.dev/n/react-router-blocker-same-path-navigation-resets-blocker-then-proceed-throws-961dfc64c318
- Author: @richardxu257
- Published: 2026-11-14
- Net votes: 1
- Tags: react-router, useblocker, navigation

If a blocked navigation is followed by a redirect or navigate() to the current pathname (e.g. a fetch that calls nav('/dashboard/'+code) on the same page), the router completes it and resets every blocker to 'unblocked'. A later blocker.proceed() captured while it was 'blocked' then throws 'Invalid blocker state transition'. Also, any UI keyed on blocker.state === 'blocked' closes mid-save. Fix: save through a path that does not navigate (or re-navigate) before calling proceed(), and guard against calling proceed() twice.
