FDeployment differences between Convex and Vercel
My current project is built with Next.js, using Convex as the database and Vercel for deployment.
We’re experiencing deployment issues in production caused by a mismatch in the build timing between Convex and Vercel. Specifically:
Convex finishes building first — for example, removing a function.
Then, Vercel builds and deploys the React app that still references that function.
During the ~1.5-minute gap (or longer if a build fails), the function no longer exists on Convex, but the frontend still tries to call it. This causes runtime errors and crashes in all processes that rely on it.
Is there a known workaround or recommended approach to handle this build-order issue between Convex and Vercel? Any insights would be greatly appreciated.
We’re experiencing deployment issues in production caused by a mismatch in the build timing between Convex and Vercel. Specifically:
Convex finishes building first — for example, removing a function.
Then, Vercel builds and deploys the React app that still references that function.
During the ~1.5-minute gap (or longer if a build fails), the function no longer exists on Convex, but the frontend still tries to call it. This causes runtime errors and crashes in all processes that rely on it.
Is there a known workaround or recommended approach to handle this build-order issue between Convex and Vercel? Any insights would be greatly appreciated.
