Hello Vercel Community,

I need help diagnosing a production deployment authorization failure for an existing project.

Environment: Vercel CLI 63.1.2, Node.js 26.5.0 on macOS, Hobby plan. Files-based deployment to an existing linked project, using explicit team scope.

On October 21, 2026, around 10:47 UTC: vercel deploy --prod --yes --scope TEAM_SLUG_REDACTED returned: {"status":"error","reason":"deploy_failed","message":"Not authorized"}

Checks using the same authentication:

• Current user, team, project and previous production deployment are readable.
• Team membership confirmed OWNER.
• Local linked project/team IDs match the accessible project.
• Credential metadata shows not expired or revoked.
• No VERCEL/NOW environment variables override authentication.
• Last successful production deployment: October 21 at 01:40 UTC.

The failure output did not include a request ID or a specific failing endpoint. We have not repeated deployment attempts, changed security settings or broadened token permissions. These checks describe the October 21 investigation, not a new deployment attempt today.

What is the supported next diagnostic step to identify the rejected authorization check without another blind deployment attempt? Is there a safe read-only diagnostic or a private channel for project/request identifiers?

No credentials, project identifiers, private logs, photos or application records are included in this post.