AsyncLocalStorage Next.js Error with Cloudflare Workers

[logaretm]

Description

Initially reported by @tristanbes in this issue

I just had an outage on my production because of this. I am, as i'm typing this message, deleting all server side integration with sentry that I followed from your docs.

Cannot call this AsyncLocalStorage bound function outside of the request in which it was created.

Environment:

• Next.js: 15.5.9
• @opennextjs/cloudflare: 1.14.8
• @sentry/nextjs: 10.33.0
• Deployment: Cloudflare Workers
• Cloudflare Workers compatibility_date: 2025-11-17
• Cloudflare compatibility_flags: nodejs_compat, global_fetch_strictly_public

Symptoms encountered:

• AsyncLocalStorage errors when using Sentry.captureRequestError in the onRequestError hook (maybe with addBreadcrumb too)
• Server-side Sentry initialization causes silent failures or "Server failed to respond" errors

Current workaround:
I've removed all server-side Sentry integration (deleted sentry.server.config.ts and sentry.edge.config.ts) and only kept client-side error tracking via instrumentation-client.ts. Client-side Sentry works fine.

The withSentryConfig wrapper in next.config.ts still works for source map uploads and the /monitoring tunnel route.

Is there an ETA for OpenNext/Cloudflare Workers support? Would love to have full-stack observability back. Happy to help test any beta/canary versions.

I haven't reproduced it yet, but it might be related to #18700

[linear]

JS-1480

[inooid]

I've created a reproducible repo with the last working version (and a PR with the latest non-working version) if that helps. This repo simply consists of:

1. npm create cloudflare@latest -- my-next-app --framework=next
2. npx @sentry/wizard@latest -i nextjs (replacing the DSN and config with env vars)

✅ The main branch is running @sentry/nextjs@10.32.1 and is confirmed to work
❌ The update-to-10-33-0 branch is running @sentry/nextjs@10.33.0 which does not work.

In order to run:

1. Checkout the repo
2. npm install
3. Setup .env with a SENTRY_DSN
4. npm run preview to run opennextjs-cloudflare build && opennextjs-cloudflare preview
5. Head to the localhost app /sentry-example-page and/or /api/sentry-example-api (e.g. http://localhost:8788/sentry-example-page)

On main it looks like this as expected:

On update-to-10-33-0 it looks like this:

Let me know if there's anything else I can do to help out

[logaretm]

Thanks for the reproduction, it is indeed caused by #18700. I'm working on a fix right now.

[github-actions]

A PR closing this issue has just been released 🚀

This issue was referenced by PR #18889, which was included in the 10.36.0 release.