a month ago
For some reason, our deployments keep failing because of things happening that are breaking our watch paths.
First, I started noticing that none of our builds were actually getting deployed because they were all skipped. Apparently, railway.json defined watch paths stopped working suddenly without me being notified.
Then we switched to just hard coding it into the settings for each service.
Then today, I noticed things were being skipped again! It took so much time to figure out what was wrong, and it looks like the Metal Build switches were turned on. This was not something I did. This was rolled out by your team automatically I guess, which completely skipped all of our builds.
This is not OK. We're not at all happy with how something so core to a product can go wrong.
How can these "automatic" rollouts be stopped, especially when they're breaking our deployments?
Also, why can't this be asked directly to Railway privately? They've disabled contacting them directly completely. This is complete bs.
1 Replies
Status changed to Awaiting Railway Response Railway • about 1 month ago
a month ago
We're aware of an issue where watch paths are not being correctly evaluated in certain deployment scenarios, causing builds to be incorrectly skipped. This has been escalated to our product team. Your mem0 service is currently in a SKIPPED state consistent with this. You can redeploy affected services manually via the Command Palette (CMD+K, then "Deploy Latest Commit") or the Redeploy option in the deployment menu to get them running again in the meantime. Regarding private support, Private Threads are available on the Pro plan.
Status changed to Awaiting User Response Railway • about 1 month ago
a month ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • about 1 month ago