17 days ago
Hi - I have what I think is a bug, but I'd love ideas on hwo to avoid it. I have a Flask app deployed. It appears it was automatically deployed ~2 hours ago. I realized an hour ago that it wasn't working (502 error), and when I went to investigate, I saw the note that it had been automatically redeployed, but the deploy logs were completely empty. I tried restarting it, which did nothing. I then tried re-deploying it, which fixed it.
I guess my question is: is this is a bug, or is there something in my configuration I should have an eye on to prevent automatic redeploys from being "empty" in this way?
2 Replies
17 days ago
Same issue - my production deployment just has the deploy logs completely empty. When I try to redeploy old builds, the menu is just empty. I assume this is an issue on Railway's side.
esskor-infra
Same issue - my production deployment just has the deploy logs completely empty. When I try to redeploy old builds, the menu is just empty. I assume this is an issue on Railway's side.
17 days ago
Seems fixed. This is a very scary error to happen and took down production for a few hours. I hope Railway releases a statement on why this happened and what they're going to do because these are the types of errors that make customers lose trust in a company.
Status changed to Awaiting Conductor Response brody • 17 days ago