This looks something like a soft lock, and since you haven't exceeded any memory limits this would be an issue with your code.

I would highly recommend adding more verbose logging so that you can find out what it was doing when it froze.

I think you meant deploy logs?

But yes, that means your code is freezing, adding as many verbose logs as possible here is what will help you to figure out what the app is doing before it froze so that you can pinpoint the code issue.

I've been in your shoes before, It's tricky but adding logs will help you.

But beyond this advice there isn't much we can do here to help as this wouldn't be an issue with the platform and because we aren't able to offer coding help.

So I thought it might be my code, but the problem doesn't occur when I'm doing local testing. In this case it should also occur, if this were the situation, as it would go through the same piece of code. and since we are dealing with docker, local and cloud executions have the same configurations

Execução Local:



Railway:

Unfortunately working locally doesn't mean there isn't an issue with the code, I assure you better logging will help you pinpoint the issue.

Additionally, you may have better luck with self hosting browserless via our browserless template instead of installing chrome.

Please see the browserless template, and check out it's overview for code examples.

https://railway.app/template/browserless