Why This Happens
In Next.js, the notfound() function was called. This is one of the most common Next.js errors developers encounter. Understanding the root cause helps you fix it quickly and prevent it from recurring.
The Problem
import { notFound } from 'next/navigation';
const data = await fetch(url);
if (!data) notFound();The Fix
// This is intentional — create app/not-found.tsx
// to customize the 404 pageStep-by-Step Fix
- 1
Identify the error
Look at the error message: NEXT_NOT_FOUND. This tells you exactly what went wrong.
- 2
Find the cause
Check the stack trace to find which line of your Next.js code triggered this error.
- 3
Apply the fix
Use the corrected code pattern shown above. Test to confirm the error is resolved.
Bugsly catches this automatically
Bugsly's AI analyzes this error pattern in real-time, explains what went wrong in plain English, and suggests the exact fix — before your users even report it.
Try Bugsly free