Error AtlasError Documentation and Resolution

React recovered from a concurrent rendering error by switching to sync render

There was an error during concurrent rendering but React was able to recover by instead synchronously rendering the entire root.

React encountered a concurrent rendering problem and fell back to synchronously rendering the full root to recover.

React error #520runtime
There was an error during concurrent rendering but React was able to recover by instead synchronously rendering the entire root.
  • A rendering path is not behaving safely under concurrent rendering.
  • Side effects or unstable data during render caused React to abandon the concurrent attempt.
  • A Suspense or async boundary exposed a rendering path that only fails under concurrency.
  1. Reproduce the issue in development and inspect the underlying rendering error.
  2. Review render logic for side effects, unstable values, and assumptions that only work in synchronous rendering.
  3. Check nearby Suspense and async boundaries to find the component that triggered the fallback.
React Docs: Minified React error #520
React error #520 concurrent rendering recovered by sync render | Error Atlas