Hey there! We've found the following might help you get unblocked faster:

• 🧵 NextJS Error: Application error: a server-side exception

• 📚 Railway vs. Vercel

If you find the answer from one of these, please let us know by solving the thread!

Hey, one of the reasons for higher page loading time is when your database and service are not in the same region. Can you confirm this by checking each service to verify they're in the same region?

can an employee go into the project and test the function? see whats wrong with it?

how do i see if theyre in the same reigon they are the same - although i am based in the UK currently and it says US as when i started development i was in the US - would this be a problem?

I'm afraid not as that does not look like to be a Railway problem and Railway does not offer support for problems on your service.

They are in the same region, and differing region wouldn't cause it to hang. Just be slightly slower. That is not the issue.

Do Postgres logs confirm the connection has been established?

is there anything i could show you to tell what the problem is?

um let me check

oh no i hadnt checked the postgres logs they seem to have many errors so i can look through those now, here are the errors if you know what the problem is

That looks like to be normal, is your entire website with slowness or is it specific page?

no only one button but i think that is because so far that's the only one i can test that does anything more than just writing to the database or moving around the application

If the rest of your website is functioning normally and only that button is causing an issue, then my guess is that the feature you've implemented is simply too slow.

Can I know exactly what it does? Is it a simple insert or does it perform multiple read and write operations?

Can you confirm that the rest of your queries (the most simple ones, like a single read) are working properly too? That would eliminate a lot of issues that I'm thinking of.

The L4 ROI computation performs 4-6 sequential database operations per request: it first checks/creates a company record, then queries L1 operational data (budgets/employees), L2 allocation weights, and L3 benefit weights, processes this data through calculation logic, and finally creates or updates an L4 snapshot record.

Regarding simple queries - yes, I can confirm that basic single-read operations are working properly. The server health endpoint responds instantly, and simple database connection tests complete in 1-2ms. The issue is specifically with the complex L4 computation that performs multiple sequential database operations and data processing.

Although the button will only time out after 15 mins if left without a timeout addition - also when that happens logs say something like "client has closed the request before the server could send a response" with HTTP status 499.

If it's 4-6 sequential table scans on a big table, then yes, that might take a lot of time. However, if most of them are just executing simple queries with database indexes, then I would look further into what's happening.

If I were you, I'd set up tracing (Sentry can do that btw) or simply use console.logs (or print, depending on your language) to find the slowest operation.