u/khalon23
⌘K
NextBlock™ CMS Just submitted our application for **NextBlock CMS**! 🚀 NextBlock is an open-source, full-stack CMS framework built natively for **Next.js 16 (App Router + RSC)** and **Supabase (PostgreSQL JSONB)**. We’ve focused on: * **Zero-Config 1-Click Deploy:** Automated Supabase database migrations on build. * **100/100 Lighthouse Defaults:** Tiptap visual editor renders PostgreSQL JSONB directly into React Server Components, eliminating client hydration overhead and HTML sanitization taxes. * **Cortex AI & Native MCP:** Model Context Protocol server support (`/api/mcp`) for deterministic, schema-constrained block synthesis. * **GitHub:** https://github.com/nextblock-cms/nextblock * **Live Sandbox:** https://cms.nextblock.dev Looking forward to the review process and collaborating with the Vercel DX team! 🧱
Axyl1410 Hi! I applied for the Summer 2026 Vercel OSS Program, but I’m not sure whether my application was successfully submitted. I also didn’t receive a confirmation email. Is there any way for applicants to verify whether their application was received, or is there normally no confirmation email after submitting the form? I’d like to avoid submitting a duplicate application if my original submission went through. Thanks!
Thetredisheritagehospitality 8146 Update: this is bigger than a GitHub trigger issue. I created a Deploy Hook for main (bypasses GitHub entirely) and triggered it via a plain GET request. The API accepted it and returned a job: {"job":{"id":"IC16eOMd3SbCJcRj4ZyY","state":"PENDING","createdAt":1788257683138}}. Over a minute later, no new deployment ever appeared in the Deployments list -- it never left PENDING or showed up anywhere. Since a Deploy Hook is Vercel's own internal API and doesn't touch GitHub at all, this rules out the GitHub App/webhook as the cause. Something in the build/deploy queue for this project (prj_uBPbBA45qDtmn7S6AwZymcRinmWG, team thetredisheritagehospitality-8146s-projects) appears to be stuck or not processing jobs at all. Would appreciate someone from Vercel looking at this project's queue directly.
Jacob Paris There's two issues here - one is our fault: the deploy hooks remain PENDING after they've failed - the reason it failed is listed as `rewrites[0].source` which should mean the regex in the first rewrite in your vercel.json is invalid Can you try changing that and see if it allows you to build, and if so can you share what the value is here?
pranav27 Hi @jacobparis — I'm hitting what looks like the exact same underlying bug on a different project. Same symptoms: Hobby plan, deployments silently stopped triggering (last successful was 31225c8, ~9 days ago), and a manually-triggered Deploy Hook returned a job that stayed stuck on PENDING forever and never showed up in the Deployments list: {"job":{"id":"iOLcWtyleAmQ1F0CArI4","state":"PENDING","createdAt":1788646527345}} Project: trust-rate, team: trust-rate-know-who-to-trust. One difference from the OP's case: I don't have a rewrites key in my vercel.json at all (only crons), and no rewrites/redirects in next.config.ts either — so it's probably a different underlying build failure specific to my project, but the same "Deploy Hook silently stuck on PENDING instead of showing FAILED" symptom you already confirmed is a bug. Could you take a look at what's actually failing for this project?
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.
VigorFlow I can confirm the same issue with the official Vercel MCP integration in ChatGPT. OAuth completes successfully and list_teams correctly returns my authorized team. However: * list_projects returns an empty array * get_project using the exact Project ID returns 404 Not Found * the project exists and is accessible normally in the Vercel Dashboard * the project is explicitly selected in the OAuth authorization configuration I also reconnected the integration, reauthorized the team/project, completed “Allow Access”, refreshed ChatGPT, and verified the exact Team ID and Project ID from the Vercel Dashboard. The result remains unchanged. This appears to be an OAuth project-scope / MCP mapping issue rather than a deployment 404. No deployments or write operations were performed during testing.
Normanhon 1800 Thanks for the automated guidance. Could a human from the Vercel MCP team investigate this project-access discrepancy? The official Vercel integration in ChatGPT identifies my Pro team, but `list_projects` returns `[]`, `get_project` returns 404, and `list_deployments` returns 403. The signed-in dashboard shows the project. Reauthorization has not resolved this. Only one deny-only bootstrap submission was made, containing no consultation application, credentials or customer data. Its initial receipt reported `INITIALIZING`, `target=preview`; the support assistant later reported `READY` on the production target. That later statement remains unverified. Passing Attempt 1 source checks do not establish the deployment’s actual state. Could your team please: 1. Verify the MCP OAuth principal’s team/project access mapping and explain the inconsistent reads. 2. Reconcile that same original deployment against authoritative records: ownership, requested versus actual target, any target-change history, build/source identity, aliases and protection. 3. Provide an approved private channel for identifiers, the support conversation and redacted diagnostic evidence, plus a read-only verification step. The AI > Vercel MCP support form directed us here because this Beta product receives community-only support. Please route this to a human MCP owner and provide a tracking reference. This request authorizes read-only investigation only. No second deployment or recreation, promotion, domain/alias changes, protection changes, or Production changes are authorized. Production remains No-Go.
Jacob Paris I've temporarily unsuspended the store, I think it re-suspended itself for still being over the limit — if you remove a few files to get it below the Hobby limits then it'll remain unsuspended this time, but either way you can get your files out now
Dzirnavu113a 1462 Hello, I have the same issue with my Vercel Hobby Blob store. My store bf-latvija-wordpress-blob is blocked after exceeding the Advanced Operations limit (2.2k / 2k). This Blob store contains the SQLite database for my WordPress site, so the block currently prevents WordPress from reading the database and saving any changes. I also tried the one-time unblock form, but it says: "This endpoint only works for teams that are currently soft-blocked." Could you please temporarily unsuspend/unblock my Blob store so I can regain access to my WordPress database and migrate it to another storage solution? I am not requesting additional quota. I only need temporary access to recover my existing data. Thank you!
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.
PEARL Nueroscience @amyegan I replaced 'unique-path' with my project ID and it still gives me a 404 error. Can you please help?
