please tell me you have access to that docker volume :) , otherwise …. Im dead

Yes I understand it seems incredibly strange that a deployment for 11 months can work seemingly just fine and then suddenly break, and I can understand how that looks like a platform issue but I assure you it's not, with the information I was previously provided I couldn't have begun to tell you exactly why it worked before and why it stopped, all I knew at the time is that "application failed to respond" is one of the most asked about issues with one of the easiest fixes and the advice previously given was not worth discarding because it had worked before. However, I do apologise for prematurely marking your previous thread as solved before we got to the root cause.

With the extra information added in this post it looks like the application had come back online after a redeploy, meaning the application was likely in a locked up state and was not replying to the incoming requests despite not outright crashing, there's unfortunately not much Railway can do in this situation without active health checks.

As for the missing data, there's a few things that can cause this, the first issue that springs to mind is that the application wasn't utilising a volume correctly, for example you had a volume mounted but the data was not being saved to the location of the volume, if this is the cause of the missing data, then there is no way to recover the data since the data was written to the empherial container storage. If the volume does in fact have data in it (you can tell by it's disk metrics being above 145 or so MB) then there could be other issues like the application had auto updated upon redeploy and now expects the volume to me mounted elsewhere, going to need more information on this though.

thanks it was great working with you guys! will have to move out then :(

I'm sorry to hear that, but I would be happy to go through some debugging steps to figure out what exactly happened to the data and help you prevent it in the future if you change your mind.

Hey g3org3,

I'm really sorry about this. It looks like your database was local on your deployment (SQLite perhaps?), and they would be wiped on each redeploy as they are ephemeral container storage. For persistent storage, you'd want to use Volumes instead.

The re-deploy happened because Railway may move your service to other machines to ensure you have sufficient resources required for your workload to function performantly. When this happens, you’ll see a new deployment in your service’s deployment history.

Unfortunately, we're unable to help you recover the data.