Sentry Next.js Not Sending Events
Quick answer
In Next.js, missing events usually come from blocked requests, tunnel misconfiguration, a missing instrumentation file or source map upload problems. Confirm network requests, then the SDK setup.
Most likely fix: Check the client request
How to fix it
Try these in order — the most common fix is first.
1. Check the client request
- Look for the envelope request in DevTools
- Enable tunnelRoute if it is blocked
Did this fix it?2. Check SDK setup
- Re-run the Sentry wizard for Next.js
- Confirm DSN is set for client, server and edge configs
- Enable debug: true and read the console output
Did this fix it?3. Check Sentry's Next.js troubleshooting page
- Compare your versions with the documented requirements
Did this fix it?
Symptoms
Next.js errors on client or server never show up in Sentry.
Why it happens
- Ad blocker on client requests
- Tunnel route rewrite not forwarding 429 and headers
- Config not loaded on server or edge runtime
- Build did not upload source maps
This guide also covers
- sentry nextjs not working
- sentry nextjs not sending errors
Still not working?
If Sentry keeps failing, you're not alone. See every Sentry problem users report or the alternatives people switch to.
Have an app idea? Our small team builds any software: web and mobile apps, games, desktop, AI tools. Price agreed together.
Talk to usOther Sentry errors
- Sentry Source Maps Not Working
- Sentry Events Not Showing Up
- Sentry Blocked by Ad Blockers (Tunnel Fix)
- Sentry Quota Exceeded: What Happens and How to Fix It
- Sentry Too Many Alerts and Noisy Errors
- Sentry Alert Emails Not Received
- Sentry Self-Hosted Upgrade Failed
- Sentry Spans and Performance Quota Running Out