here's the screenshot for more context

Hello,

This would be an application level issue.

Unfortunately we do no have any more observability into what your code is / is not doing than you would, thus we would recommend adding verbose logging to help you narrow down why your code stopped doing what it was supposed to.

Hello,
For more context, the last changes was 2 months ago, and everything was working well until yesterday. I don't believe this is an application level issue. How could the code suddenly have an error if there was no change?

I'm sorry but we don't have any observability into what your code does or doesn't do, thus was have no way of answering what went wrong at your application level.

You keep saying it was at the application level, but I'm not talking about whether the code ran correctly not not. I'm saying it didn't run at all for a few hours yesterday and only started again after I restarted the server.

My question is: In the last 2 months, how can an application server error happen for a few hours and then fix itself without any code change (on my end), and after I restated the server (your end)

If this was a question about why a Railway CRON job didn't run that would be a different story, but you are using an in-code cron scheduler and thus we have no way to tell you why your code didn't do what you expected it to, code change or not, best guess is that the code got into a bad state and locked itself up.

I'm sorry but we can't provide further assistance on this matter.