Possible compatibility issue with next 16.2?

[boreal veldt]

Howdy, we're running payload in production and recently bumped next to 16.2 from 15.5.14. After doing so, we started to notice a really weird behavior where any request that would have normally resulted in a 404 started to throw a 500 error. We isolated it down to the next dependency. When we roll back to 15.5.14, all works as expected, but on 16.2 we start seeing 500s. Very strange!

In logs we aren't seeing anything helpful. Previously

We aren't doing anything crazy with middleware or error handlers, all standard stuff. It doesn't seem to be route/collection specific either.

We're going to downgrade - but wanted to drop a line in case there's something up with the next bump?

[hardy tiger]

New Community-Help Thread Created!

Help is on the way! To mark it as solved, use the /solve command. In the meantime, here are some existing threads that may help you:

Documentation:

• Sentry Plugin - Options
• Installation - Adding to an existing app - 3. Add the Payload Plugin to your Next.js config
• Using Payload outside Next.js - Importing the Payload Config outside of Next.js - Troubleshooting

Community-Help:

• Best place for a studio to deploy a growing number of Payload projects?
• next-payload-demo
• Postgres causing problem on cloudflare workers for deployment