⌘K
system There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes. community.vercel.com/t/debugging-404-errors/437 A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.
Pasha Thank you for the reference. I checked the suggested article, but I believe our issue is different from a typical deployment or website routing 404. The error occurs when the existing Vercel Connector calls the Vercel REST API: GET api.vercel.com/v2/user Response: 404 / not_found / User not found I have independently verified in the Vercel Dashboard that my account is an Owner of the relevant Team. The issue appears to involve the Connector's authorization principal or identity mapping, rather than a missing website page or deployment route. Could a Vercel Connect engineer or maintainer please
system There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes. community.vercel.com/t/debugging-404-errors/437 A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.
Nitro-Shawn Hi, just bumping this up again. Currently blocked on this feature flag, would greatly appreciate someone taking a look when they can!
Nitro-Shawn Hi can you please acknowledge my issue or let me know if I'm requesting support in the wrong place? The connect SDK says to contact vercel to get access to this function, and Support says to use the community regarding Vercel Connect.
