Hey everyone we are running an issue where pushing a change to our repo rebuilds both of our apps (cms and web). The cms app is fine but the web part is no longer accessible throwing this error when visiting the website:
It’s great to see you here, @mezotv! Thank you for posting and welcome to the Community
Have you had a chance to check out our debugging 404 errors post? It might be helpful while you’re digging into this.
Looking at your issue, it seems like Vercel is rebuilding both apps in your Turborepo even when only non-app files are changed and as a result, the web app ends up deploying in an invalid state.
This usually happens because Vercel’s default behavior is to rebuild all linked projects whenever any file changes, even if those changes don’t affect the apps themselves.
A few things you can try:
First, you can configure an ignored build step in your web app’s vercel.json so that Vercel only rebuilds when certain files change:
Next, since you’re already using Turborepo, you can take advantage of Turbo’s built-in filtering. In your Vercel project settings, set your build command to:
turbo build --filter=web...
This ensures that only the web app (or its dependencies) gets built when relevant files are updated.
You can also double-check your turbo.json configuration to make sure dependency mappings are set up correctly, so Turbo knows when each app actually needs to rebuild.
Thanks so much for sticking with this and for sharing the repo + screenshots and I’m really sorry this is still happening, especially now that it’s impacting your business.
From what you’ve described:
marble-app (cms) is fine
marble-web shows the Vercel error page with 404: NOT_FOUND
GitHub says “Vercel – marble-web – Deployment has completed”
But that deployment can’t be found in the Vercel logs / dashboard
…this looks less like an Astro/Turborepo issue and more like Vercel not being able to resolve a deployment for the domain, which is what triggers that NOT_FOUND page.
I had a quick look at your repo and setup:
apps/web – Astro app (web)
apps/cms – Next.js app (cms)
Turborepo is configured with a shared build task in turbo.json
That setup is totally reasonable for two separate Vercel projects (marble-web and marble-app) using monorepo support.
At this point, because the deployment is “completed” in GitHub but apparently missing when you hit the domain, we’ll need to look at project-level logs internally. To help us dig in, could you share a bit more detail:
Which domain(s) are affected?
For example: marblecms.com, www._____, or a different custom domain.
Is the 404 happening on the Production domain only, or also on Preview deployments?
Which Vercel project owns the “web” domain?
In your Vercel dashboard, under Projects → (marble-web) → Domains, can you confirm which domain(s) are attached there?
Also double-check that those same domains are not attached to marble-app at the same time, as that can cause routing issues.
An example commit + request ID
A link to a GitHub commit where:
marble-web check says “Deployment has completed”
…but visiting the web URL shows 404: NOT_FOUND.
The Request ID from the Vercel error page (the long fral::... string on the 404 screen) from one of those failing requests.
Current build settings for marble-web
In Project Settings → Build & Development, what are you using for:
Root Directory (I’m assuming apps/web)
Build Command (e.g. pnpm turbo build --filter=web... or similar)
While we dig into the NOT_FOUND behaviour, a few things you can try to reduce how often this bites you:
Ensure only relevant commits trigger web builds
Using Turborepo’s filtering in your Build Command (e.g. pnpm turbo build --filter=web...) helps limit when the web app rebuilds.
Use Ignores for non-app changes
Instead of rebuilding on README / config-only changes, you can use the Ignored Build Step feature in your project settings (or ignoreCommand in vercel.json) so that these commits skip a deployment entirely and keep the last known-good one active.
Let me know the answers to the questions above and I’ll keep this thread updated as we learn more.
I just checked the logs for your most recent production deployments. The one that you rolled back to shows the normal sort of output file tree I would expect, but the one that threw a 404 doesn’t match. So that explains the 404 at least. The deployment succeeds and is found, but there’s no homepage available.
Now we need to figure out why the deployment output doesn’t match. What changes happened between the two deployments? Any configuration changes in the code or Vercel project?
Thanks to @anthony-shew we fixes this, our turbo.json file was missing the “.vercel/**” output so cache hits didn’t work properly. Thanks for the patience everyone!
