Yes, I’m aware of that, but this is really strange. The /api/bots/create-user route is something I worked on 5–7 days ago, and we haven’t touched it since. I wouldn’t reach out for support if I believed the issue was in my code—I genuinely think the problem lies in the deployment.
Let’s think through this logically and draw some conclusions.
First, as I mentioned, I haven’t worked on that part of the code for over a week, and I’ve deployed the app over 100 times since then—literally—without encountering this error or anything similar.
Second—and even more important—I was able to deploy version v48 (just as an example) without any issues. But starting around version v54, I began running into this error. Naturally, I suspected it was related to some recent changes in the code. So I checked everything thoroughly, even redid parts, but nothing pointed to that route or anything related.
I tried again—it still didn’t work.
So I thought: let me go back to the last version that worked—v48.
Guess what? That version, and even ones before it, now fail too.
So the logical conclusion in my mind is that something has changed on Vercel’s build side. It’s now starting to flag or complain about the /api/bots/create-user route—even though it’s been there untouched for over a week.