Edge runtime regions not working when integrating with Sentry

[Cow258]

Environment

SaaS (https://sentry.io/)

Version

No response

Link

No response

DSN

https://756fac6d7d514f5db62c7f0bc5a0f53e@o4504872119566336.ingest.sentry.io/4504872145059840

Steps to Reproduce

Link to the code that reproduces this issue

https://github.com/Cow258/edge-bug-demo

To Reproduce

1. Deploy to Vercel
2. Goto https://****.vercel/api/hello
3. Open DevTool for the response headers
4. You will find the region is different from 'sin1'

https://edge-bug-demo.vercel.app/api/hello

Expected Result

Expected Behavior

The region should be as same as the config when integrating with Sentry

Actual Result

I set the regions to ['sin1'], but it still global after deployed to Vercel and integrating with Sentry

export const config = {
  runtime: 'edge',
  regions: ['sin1'],
}

[getsantry]

Assigning to @getsentry/support for routing, due by Monday, April 17th at 10:58 am (sfo). ⏲️

[Cow258]

next.js/#48375

[AbhiPrasad]

Hey @Cow258, thanks for writing in! This is a known issue - we are tracking things related to it in this GH issue: getsentry/sentry-javascript#7450, so closing this issue since it's duplicate.

[AbhiPrasad]

Until this is fixed, you can use the excludeServerRoutes option to stop adding Sentry instrumentation to your edge routes to unblock yourself.