Failed to check for database diff: Maximum call stack size exceeded — Cannot republish

Bugs
, , , ,
1

I’m unable to republish my application. The deployment page shows a persistent yellow banner:

“Failed to check for database diff: Maximum call stack size exceeded”

The green “Republish” button is visible but clicking it doesn’t work — the deployment never starts.

About my project:

  • Full-stack TypeScript app (Express + React/Vite)

  • PostgreSQL database with approximately 990 tables (it’s a large enterprise ERP system)

  • Using Drizzle ORM with schema definitions across multiple files

  • Autoscale deployment (4 vCPU / 8 GiB RAM)

  • Last successful publish was about 4 days ago

  • Production database is connected and working fine

What I’ve tried:

  1. Removed drizzle.config.ts entirely — the banner still appears even with no drizzle config file present, so there’s nothing for the diff checker to compare against

  2. Reduced production tables from 993 to 630 — dropped all unused tables thinking the volume was causing the crash. Banner persisted.

  3. Re-synced production tables back to 989 to match the code schema — still no change

  4. Renamed the .drizzle migrations folder so no migration history exists — didn’t help

  5. Multiple republish attempts across different days — same result every time

My theory:
The database diff checker in Replit’s deployment system appears to crash with a stack overflow when processing a large number of tables (~990). This seems to be a platform-level limitation rather than a project issue, since:

  • The app runs perfectly in development

  • The production site is live and working (just running an older version)

  • Removing the drizzle config doesn’t bypass the check

  • The error occurs before any build or deployment step begins

What I need:
A way to either skip the database diff check entirely, or a fix for the diff checker to handle large schemas. Alternatively, if there’s a manual way to trigger a deployment that bypasses this check, that would work too.

Production URL: www.acmenetsuit.com

Any help from the team or community would be greatly appreciated. This has been blocking all updates to production for several days now.