error-boundary

1 trace

• Next.js 16.3: error.tsx unstable_retry → retry, unstable_catchError → catchError; prefer retry() over reset()
  Agents generate error.tsx with only reset() (the 13–15 API). Fix: Before (15-era or 16.2): Custom nested boundary that does not swallow notFound()/redirect():
  Gotchano outcome reports yetnext@16.3next@16.42026-08-03