2 months ago
This never happened before
Attachments
7 Replies
2 months ago
Your build failures coincided with a platform-wide deployment issue that was degrading builds across all regions between approximately 21:45 UTC and 02:17 UTC on Aug 18-19, which has since been resolved. Redeploying now should succeed normally.
Status changed to Awaiting User Response Railway • about 2 months ago
Railway
Your build failures coincided with a platform-wide deployment issue that was degrading builds across all regions between approximately 21:45 UTC and 02:17 UTC on Aug 18-19, which has since been [resolved](https://status.railway.com/incident/YYU63JUO). Redeploying now should succeed normally.
2 months ago
This has been happening the whole day I was deploying without issues until today
Status changed to Awaiting Railway Response Railway • about 2 months ago
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
Apologies for the trouble. Your second screenshot confirms the build error was "Failed to connect before the deadline," which was caused by two back-to-back deployment incidents that ran from 21:45 UTC on Aug 18 through 02:17 UTC on Aug 19. Those incidents are now fully resolved, your build queue is clear, and no builds are stuck. Please try redeploying now - builds should complete normally.
Status changed to Awaiting User Response Railway • about 2 months ago
Railway
Apologies for the trouble. Your second screenshot confirms the build error was "Failed to connect before the deadline," which was caused by two back-to-back deployment incidents that ran from 21:45 UTC on Aug 18 through 02:17 UTC on Aug 19. Those incidents are now fully [resolved](https://status.railway.com/incident/YYU63JUO), your build queue is clear, and no builds are stuck. Please try redeploying now - builds should complete normally.
2 months ago
Still issue
Status changed to Awaiting Railway Response Railway • about 2 months ago
2 months ago
Your service actually deployed successfully at 02:54 UTC and is running and serving traffic normally right now. The failure you are seeing is from a subsequent deploy attempt three minutes later that did not complete, but it did not replace the working deployment. Please try deploying once more, as the build infrastructure has fully stabilized since the incidents resolved.
Status changed to Awaiting User Response Railway • about 2 months ago
2 months ago
kk it works now. i think
Status changed to Awaiting Railway Response Railway • about 2 months ago
Status changed to Solved Railway • about 2 months ago