Your workspace compute usage is $0.48, well within the $5 trial credit, so no compute limit is blocking deployments or affecting your running service. The "usage limit reached" warning is from your Agent usage ($1.52) exceeding the $1.50 Agent hard limit, which only disables AI features (Canvas chat, deployment diagnosis) and does not block deployments or stop services. You can adjust that limit at railway.com/workspace/usage under "Update limits." Your recent deployments are failing due to a build error in your source code (visible in the build logs for each failed deploy), which is unrelated to any usage limit.

Thanks. I have another issue that is preventing me from diagnosing the failed deployment.

Every time I open the Build Logs for failed deployment, Railway dashboard/page crashes, so I cannot reliably access the compiler output.

Could you please check the latest failed deployment for Robust Site Production and tell me:

1. the first actual build/compiler error, including the filename and line number;
2. whether there is any Railway-side issue causing the Build Logs UI to crash for me;
3. if possible, provide the relevant raw build-error lines from the failed deployment.

I understand the build itself may be failing because of my source code. I am not asking Railway to debug the application code, I just need access to the actual build error because the Build Logs page keeps crashing when I try to view it.

The latest failed deployment's build logs show the error is in client/src/components/PayPalButton.tsx at line 71, column 15 - the Vite/esbuild transform step rejects an unexpected Unicode object-replacement character (U+FFFC) on that line, where orderId: , contains a non-visible character instead of a value. The build ran npm run build, the client's Vite build transformed 98 modules successfully, then failed on that file. We have no visibility into why the Build Logs page is crashing in your browser, but the build log content above is the complete error from that deployment.

Hi, thank you — fixing the U+FFFC character solved the build and the deployment is now green.

I have now tested the live PayPal checkout on the deployed website. When I click PayPal, the checkout reports “Payment failed. Please try again.”

Because Railway logs still crash for me when I try to inspect them, could you please check the deployment/runtime logs around my latest payment attempt?

In particular, could you tell me whether any of these requests failed and provide the exact status/error:

GET /api/paypal/setup

POST /api/paypal/order

POST /api/paypal/order/:orderID/capture

Please include the HTTP status code and the underlying error message from the first failing request. I’m not asking you to debug the PayPal integration itself — I need the raw runtime/server error because I cannot reliably access the logs in Railway.

Having looked into this, the issue appears to be in your application code or configuration rather than the Railway platform itself, which puts it outside what Railway support can resolve directly.

This is exactly the kind of problem the Railway community is good at, so we'd like to open your thread as a community bounty. Railway pays a bounty to the community member who solves it, and threads like this usually get picked up quickly.

Opening it makes this entire thread public, including everything already posted. Nothing becomes public until you decide. Use the buttons below.

• Open to the community - Before you click, take a moment to edit or remove anything you'd rather not share. The thread becomes publicly visible right away.
• Keep it private and close the thread - Nothing becomes public and the thread closes.