Hey! We were not experiencing any issues at this time, no. It seems like everything has deployed since your reported this issue. Are you still seeing slow build/deploys?

Yeah, looks like all the deployments have finished now.

You may close this ticket.

However, would you be able to escalate on this to figure out why this happened? The common thing about these services was that I upgraded all of their npm dependencies. In the past, I also experienced a weird behavior with railway when I upgrade my dependencies. Any commits I push after the dependency upgrade commit doesn't get reflected for a few hours(?) even if the deployments were successful. I suspect these two events might have a similar root cause.

--

Here's the URLs of said timed-out builds:

• Case 1

• Case 2

• Case 3 (couldn't link the deployment of this service-- all seems removed)

If you see that issue with dependencies not getting rolled out please open a ticket and we can look into it

Going to close as the original issue seems resolved and new deploys seem to be going out just fine

It happened again, here's another example. This one is just normal commit, no new npm dependencies. Now the builds are OK again now. This issue seems to be happening intermittently. Similar logs:

 

#5 sha256:4ca66ffdb79362fd7157174db640d24cff5594d6acc3d12193766a2fc158c2cc 40.89MB / 43.52MB 3547.3s

 

#5 sha256:4ca66ffdb79362fd7157174db640d24cff5594d6acc3d12193766a2fc158c2cc 40.89MB / 43.52MB 3552.4s

 

#5 sha256:4ca66ffdb79362fd7157174db640d24cff5594d6acc3d12193766a2fc158c2cc 40.89MB / 43.52MB 3557.4s

 

#5 sha256:4ca66ffdb79362fd7157174db640d24cff5594d6acc3d12193766a2fc158c2cc 40.89MB / 43.52MB 3562.5s

 

#5 sha256:4ca66ffdb79362fd7157174db640d24cff5594d6acc3d12193766a2fc158c2cc 40.89MB / 43.52MB 3567.6s

 

#5 sha256:4ca66ffdb79362fd7157174db640d24cff5594d6acc3d12193766a2fc158c2cc 40.89MB / 43.52MB 3572.7s

 

#5 sha256:4ca66ffdb79362fd7157174db640d24cff5594d6acc3d12193766a2fc158c2cc 40.89MB / 43.52MB 3577.8s

 

#5 sha256:4ca66ffdb79362fd7157174db640d24cff5594d6acc3d12193766a2fc158c2cc 40.89MB / 43.52MB 3582.9s

 

#5 sha256:4ca66ffdb79362fd7157174db640d24cff5594d6acc3d12193766a2fc158c2cc 40.89MB / 43.52MB 3588.0s

 

#5 sha256:4ca66ffdb79362fd7157174db640d24cff5594d6acc3d12193766a2fc158c2cc 40.89MB / 43.52MB 3593.1s

Do you by chance know how large your image is?

When did this occur? Railway has an incident earlier -

https://status.railway.app/clxkpme3f722914e5osb5r304gf

Do you by chance know how large your image is?

Around 114MB~ ish

When did this occur?

Yesterday, June 18 1500~ GMT+8. So way before that incident

My original posts meanwhile the issue happened at June 17 2248~ GMT+8

Do you have any idea when this might occur? It seems at least from inspection to be random?

Timing wise, it seems random. Couldn't figure out yet why. I'll keep updating this thread for when I encounter it again.

Might be unrelated, but I also tried using the v2 deployer on a subset of my services (i.e.: some legacy, some v2). In my original post, 2 was using legacy, 1 was v2 but all 3 was affected by the build timeout.

Build and runtime have no relation/overlap

Unfortunately at this point we can't diagnose this issue and it seems to only occur for your application

I've created a ticket for this internally on the backlog. If we get more issues, we will circle back here