⌘K
system Thank you for bringing this to our attention. To ensure this is investigated with the necessary priority and privacy, please report all security-related concerns, potential exploits, or abuse directly to the Vercel Security Team. Please submit your report here: vercel.com/abuse Reporting via this official channel is the fastest way to reach our security engineers and ensures that sensitive information is handled in a secure environment rather than a public forum.
Jen 2568 I submitted a report on 9/28, case number 01586042
Amy Egan Thanks for sharing the case number. I'm checking with the team about it now
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. https://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.
Bùi Tuấn Pháp Thank you. That guide primarily addresses 404 errors when accessing website/deployment URLs. Our error occurs in the official Vercel MCP get_project tool, using the exact Project ID and Team ID shown in Dashboard settings. get_auth_user succeeds and returns the expected user and matching team. We have already reauthenticated and refreshed the MCP connection. Please advise on MCP-specific resource visibility, effective grants or request routing, rather than website build output, rewrites or DNS changes. Request ID: sin1:sfo1::9v9dm-1792402022775-6c5d3f2b5801
Amy Egan It is expected that the first deployment goes to the production environment. I shared a workaround in another post https://community.vercel.com/t/vercel-cli-ignores-target-preview-and-creates-production-deployment/46384#post_10
Kazu Pet Ai Thanks, Amy. In my case, the first Production-classified deployment still exists, but its status is Error. Before I retry, could you please confirm whether that failed deployment still counts as the project’s first deployment, so that the next command with --target preview will be classified as Preview? I have not deleted the failed deployment.
Jmarcelodesign 8127 Hello Vercel team, I have the same question for another existing Hobby project. Its first deployment is still retained, has target=production, and ended in ERROR despite an explicit Preview intention. The Python requirements parsing failure has been fixed in a separate candidate that has not been uploaded. The project has 37 sensitive application variables scoped exclusively to Preview. Does retaining that failed deployment ensure that the next deployment without --prod is Preview? Which official command, API parameter, project setting, or verifiable prerequisite establishes this without creating any Production bootstrap, promoting a deployment, or copying Preview variables to Production? The authenticated Vercel Help assistant told me that an ERROR record counts as the initial deployment, but also stated that the public documentation has no dedicated clause for this case. Its human-case form for CI/CD > Environments requires a paid account on my Hobby plan. I would appreciate clarification from the team through this free discussion. I can provide the project and deployment identifiers privately through an official channel if needed. No new deployment has been attempted. This request asks for clarification only, not resource changes or a paid support upgrade.
