I am seeing contradictory Personal Access Token behavior on a Vercel Hobby account. Dashboard/browser authentication otherwise works, and our repository uses Vercel CLI 59.1.4.

Latest reproduction

1. Open the authenticated token creation UI.
2. Choose a team-scoped PAT covering that team's projects.
3. Set a one-hour lifetime.
4. Click Create once.
5. The UI reports: An error occurred while creating token. Please try again later.
6. No credential value is displayed.
7. The same open browser state later shows Token Created, still with no accessible credential.
8. Close the dialog and check the fully loaded All token list three times, approximately three seconds apart.
9. The exact named token is absent each time.

I cannot determine whether the provider transaction created an internal resource, so I am not claiming success or failure. No token was available for an API test.

Separate earlier observation

On the previous day, a different fresh PAT selected as Full Account / Non-SAML reached GET /v2/user and returned HTTP 403. The test stopped immediately and that token was revoked. I do not know whether the two observations share a root cause.