#builds

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. 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.

Amy Egan There are a lot of possible causes. I hope you were already able to solve it using the tips shared by the bot. If not, it would be helpful to see the site and code to get a better understanding of what's going wrong in this case. Are you able to share a minimal reproducible example or a publicly accessible URL for the site?

Ryu Hi Zangyj1971, I don’t think another community member can reliably confirm whether CLI issue #17069 is still present in 58.0.0, but you can separate the documented workflow from the suspected bug pretty cleanly. The documented CLI behavior is that a normal CLI deploy without --prod should create a Preview deployment, while --prod creates Production. So for a fresh linked project, the safest thing to test is: vercel deploy --target=preview --logs vercel inspect <deployment-url> Then check the inspected deployment’s environment/target before using it in any release flow. For Git, Vercel treats t

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. 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.

Ryu Hi Solomon, The Functions tab only showing /api/auth/[...nextauth] is not necessarily a problem by itself. Static App Router pages will not always show up there as functions. The more important signal is the exact 404 type and which URL is returning it. I’d separate three cases: Unique deployment URL returns 404 Project/production alias returns 404 Only specific app paths like /todo return 404 Can you test the unique deployment URL from the deployment details page, not just the project alias? curl -I https://<deployment-id-or-unique-url>.vercel.app/ curl -I https://<deployment-id-or-unique-url

system The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points. vercel.com/docs/projects/domains/troubleshooting You can also use v0 to narrow down the possibilities.

Ryu Hi Hero, I’d first separate “Safari is slow to get the document” from “Safari gets the document quickly but renders a blank page for a while.” A quick way to check is to run this in Safari’s console after a slow load, then compare it with Chrome on the same iPhone: const n = performance.getEntriesByType("navigation")[0]; console.table({ dns: Math.round(n.domainLookupEnd - n.domainLookupStart), connect: Math.round(n.connectEnd - n.connectStart), tls: Math.round(n.requestStart - n.secureConnectionStart), ttfb: Math.round(n.responseStart - n.requestStart), download: Math.round(n.responseEnd - n.r

Ryu Hi babakfp, The key clue is this line: Skipping build cache since Package Manager changed from "pnpm" to "npm" After that, the workspace:* error is expected because npm is trying to install a pnpm workspace project. So I’d focus on why Vercel switched package-manager detection, not on the dependency itself. Since this repo is using pnpm@11.9.0, I’d avoid relying only on automatic lockfile detection and try Corepack explicitly. In Vercel Project Settings → Environment Variables, add: ENABLE_EXPERIMENTAL_COREPACK=1 Then keep the package manager pinned in the repository root package.json: { "pack

Ryu Hi Brian, Since manual redeploys work but Git pushes and Deploy Hooks create no visible deployments, I’d check the settings that can stop deployment creation before digging into build logs. A few quick checks: Project Settings → Git Is the production branch still master? Are ignored build step settings enabled? Is the repo connected to the same GitHub repo/branch you are pushing to? I’d also search the repo for Git deployment-disabling config: grep -R "deploymentEnabled\|github.*enabled" vercel.json vercel.ts . 2>/dev/null If you have either of these, they can prevent Git-triggered deployments

Ryu Hi Shirazatz, Your repro is already pretty strong, especially because an old green commit fails only after the CLI version changed. One workaround I’d try is making the function pattern less dependent on the exact file path: { "functions": { "api/**": { "maxDuration": 60 } } } or, if Vercel accepts the JS glob in this setup: { "functions": { "api/index.*": { "maxDuration": 60 } } } The error is coming from the functions pattern check, not from your function code, so this test should tell you whether the regression is specifically around matching api/index.js under a custom Root Directory. I’d

Don Lao problem is resolved by remote supabase integration, use API or token instead.

system The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points. vercel.com/docs/projects/domains/troubleshooting You can also use v0 to narrow down the possibilities.

js I'm seeing the same problem on one of my three projects. I've tried both Chrome, incognito Chrome, and Firefox, all with the same issue. I'm on a mac. Nextjs as well.

js And now it's fixed.

Vinaydabas611 40 viewers/day is low for 3h50 of CPU, so before pinning it on crawlers or compute, confirm your actual request count in the logs. If it's far above your real traffic, the usual hidden cause is your own app re-firing server renders --- a router.refresh() / auto-refresh on tab focus or navigation, aggressive client-side polling, or default prefetch firing a burst of RSC requests on every page. (A third-party uptime monitor on a tight interval does the same.) The tell is a repeating, multi-route request pattern in the logs that no human would produce. If real crawlers are a big share: a robots.t

Ryu Hi Adeline, Your suspicion sounds pretty reasonable. When an AI app grows from "one prompt generates everything" into multiple muses, menus, timelines, variations, etc., the fragile part is usually that too much decision-making is left inside the prompt. I'd separate this into a more deterministic pipeline: User selects / describes the party App deterministically chooses the muse/theme metadata from a fixed JSON or database table AI generates only the sections that actually need language generation Output is validated against a schema Failed or mismatched sections are retried individually, not

Ryu Hi Senseijayrome, v0 creates its own working branch off main when a chat is connected to GitHub, so if it is stuck at “Create Branch” I’d first separate repo permissions from the v0/GitHub connection state. A few things I’d check: In GitHub, confirm the Vercel/v0 GitHub app has access to AtlasJamaica/atlas-transportation-solutions-jamaica, not just your GitHub account generally. Check whether the repo has branch protection or repository rulesets that block creating or pushing branches matching v0/*. Try creating a test branch manually from main: git fetch origin git checkout -b v0/manual-test