Application does not work after deployment

[backurdi (Bachir K)]

I have created a project that does some file handling. The flow works locally but when I push to vercel the flow starts to hang at one point in the flow I do not get any error messages or anything. I have dobbelchecked all env variables and or settings all should work.

What I do with the docs is to read them using third party libraries and pass the data to openRouter.

I cannot find anything that should be different between my local or the deployment environment.

Can anyone help!

[rizbizkits (Riz)]

Hey @backurdi! I’m sorry to hear you’re facing this issue.

To help us triage and narrow down possible root cause(s), would you be able to provide the following details?

1. Are you using a framework? Is this Next.js and, if so, are you on the latest version?
2. “…the flow starts to hang at one point” — do you mean the page ends up loading endlessly in the deploy environment (i.e. on Vercel)? Have you checked the Network tab of your browser’s DevTools for any failing API endpoints?
   1. If possible, you can also include relevant deployment URLs where the issue is replicable for us to review, further

Looking forward to your reply

[backurdi (Bachir K)]

Hey Riz thanks for fast reply.

1. Yes I am using nextjs. I just bumped it to latest version to see if it helped but nothing changed

2. When I said flow I meant a flow inside the application. The deployment works fine, but the flow itself stops. It’s one of my endpoints that suddenly stops, without no error message, timeouts or anything. It just returns 200 at a point before it is completely done.

What the function does.

• It gets files urls
• depended on the file type it either downloads the file to extract the content or just passes the file link
• Calls llm through openRouter
• Updates the db based on llm response

I use Convex and openrouter in this flow

I have added 2 screenshots, one is from my local run and one from the deployed version. As you see the deployed version stays in this state while the local one runs through as expected.

[rizbizkits (Riz)]

When I said flow I meant a flow inside the application. The deployment works fine, but the flow itself stops. It’s one of my endpoints that suddenly stops, without no error message, timeouts or anything. It just returns 200 at a point before it is completely done

Interesting, would you be able to share the name of the exact endpoint (including the project name)? Is the 200 also reflected in your runtime logs despite the “stuck” flow? If so, can you include a link to the exact log line?

I’m wondering if the 200 is being sent prematurely before one (or more..) of the operations of your function is completed (i.e. missing an await). Transparently: it is difficult to deduce without being able to replicate or have eyes on a minimal reproduction to review

[backurdi (Bachir K)]

Sorry Riz I totally missed your message.

And oh god this is what happens when you vibecode. That was the issue, the function was finishing before all the elements was done. Thank you so much for the help.

[rizbizkits (Riz)]

Wonderful, I’m so glad to hear this was resolved!

[backurdi (Bachir K)]

Thanks man, love your fast and effective help. Keep it up!