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.

Thanks, but this isn't a routing 404 — the generic 404 tips don't apply here.

The 404 is only a downstream symptom: my new production build is never promoted because a required native check "Microfrontends Config Present" (jobName: mfe-config-present, source: vercel-native-check, origin: api) fails on EVERY deployment, leaving it "Staged / Checks Failed". So the custom domain keeps serving an old build.

The key problem: this project is NOT a microfrontend and is NOT in any microfrontends group, so there is nothing to configure and nothing to remove:

• Project & Team Settings → Microfrontends: no group ("This project is not a microfrontend" / "No Microfrontends Groups yet")
• • vercel microfrontends remove-from-group → "Error: Project tradenork is not part of any microfrontends group."
• So this required check is orphaned and there's no way to satisfy or disable it from the dashboard or CLI. Could a human please clear/remove this orphaned mfe-config-present check for project tradenork (team pipats-projects)? Latest blocked deployment: 3yKmJFY3svp1BUZdGVcXpErn3U2b. Thank you!

Hi Vampire,

I’d first edit out the team name, deployment IDs, and checkRun ID from the public post. They are not secrets like tokens, but they are still internal project/account identifiers.

For the actual issue, I agree this does not sound like a normal routing 404. The 404 is likely just the symptom of the production alias still pointing at the older deployment because the newer deployment is stuck behind a required check.

I’d check two places before changing app code:

1Project Settings → Deployment Checks2Project Settings → Microfrontends3

If Microfrontends Config Present appears under Deployment Checks and there is a remove/disable option, remove it and create a new production deployment. If it does not appear there, but every production deployment still gets the native check, then that points more to stale platform-side project metadata than a missing file in your repo.

Also check the deployment details page for a Force Promote option. Vercel’s Deployment Checks docs mention that production deployments are not assigned to domains until checks pass, and that checks can be bypassed with Force Promote:

https://vercel.com/docs/deployment-checks

If Force Promote is unavailable or blocked too, I would not try to “fix” this by creating a dummy microfrontends group/config, because that could make the project state more confusing.

The clean escalation summary is:

1Project is not in any Microfrontends group2Team has no Microfrontends groups3Production deployments are created but remain Staged / Checks Failed4Failing native check: Microfrontends Config Present5jobName: mfe-config-present6Custom domain still serves older production deployment7Manual promote / force promote result:8Microfrontends settings page result:9Deployment Checks settings page result:10

That should make it clear this is a stale required-check/control-plane issue, not a Next.js route or DNS issue.