Your Team encountered an unknown problem. Please reach out to our support team for details. Learn More
user_ID = p6e2poiT98qNYnMFownMGLJy
team ID = team_TreQdv5OQWPzyQGAR8qlNRc3
user_ID = p6e2poiT98qNYnMFownMGLJy
team ID = team_TreQdv5OQWPzyQGAR8qlNRc3
This appears to be the same issue I reported in my post: Deployment Error
Hi Josue,
That “Your Team encountered an unknown problem” message is usually not enough to debug from the screenshot alone, because it can happen before you get a normal build error.
First, I’d edit your post and remove the user/team IDs. They probably are not secrets like an API key, but there’s usually no need to keep account identifiers public.
Then I’d try to narrow down whether this is a project build problem or a team/dashboard problem:
npm i -g vercel@latest
vercel whoami
vercel switch
vercel link
vercel deploy
If the CLI deploy shows a normal build error, paste the first real error line here with secrets removed. If the CLI also returns the same unknown team-level error before the build starts, then it is probably not your app code.
Also check that you are deploying from the Vercel account/team that owns the project, and that the repo does not contain an old .vercel folder pointing to another team/project. A common cleanup test is:
rm -rf .vercel
vercel link
vercel deploy
If it still fails after relinking, share the CLI error text and whether the failure happens before install/build logs start.