Vercel Connect returns 404 User not found despite confirmed Team Owner membership

Hello Vercel team,

I'm experiencing an identity-mapping issue with an existing Vercel Connect integration and would appreciate technical guidance.

My current account status

I have verified directly in Vercel Dashboard that:

My account is listed as a member of the relevant Team.
My Team role is Owner.
The Team is active.
My plan is Hobby.

The issue

An existing Vercel Connector integration made the following request:

GET https://api.vercel.com/v2/user

The response was:

404 / not_found / User not found

This is confusing because my account is visibly listed as a Team Owner in the Vercel Dashboard.

What I would like to understand

Why would Vercel Connect return User not found when the account is visibly a Team Owner?
Does Vercel Connect use a separate authorization principal or connection context from the currently logged-in Dashboard account?
How can I verify which principal the existing Connector connection represents?
Is there an officially supported way to diagnose or repair the existing connection without replacing credentials or switching accounts?
Is this a known Vercel Connect Beta limitation?

I have not changed Team membership, credentials, projects, or deployments.

I can provide the Team ID and additional non-sensitive diagnostic information privately if needed.

I will not share API tokens, secrets, cookies, or Authorization headers.

Thank you for your help.

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.

https://community.vercel.com/t/debugging-404-errors/437

Vercel Community

Debugging 404 Errors

Sometimes things don’t go as expected when deploying a website. If you see a 404 on your site, that means the page or resource couldn’t be found. There are...

A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.

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 https://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 review this specific case?

In particular, I would appreciate guidance on how to diagnose the existing Connector's principal mapping and authentication context without replacing credentials or changing the current Team membership.

Thank you.