Build failed despite working last night, tried re-deploying same build no changes but to no avail

Mind sharing the link to that build?

Not the main issue here, but is there any reason for you to use Nixpacks instead of Railpack? Nixpacks is deprecated.

to the first point: https://railway.com/project/c3de73e0-7655-4bfe-900f-c65cdf3cb979/service/6a296099-350a-4ca2-a0e4-5cdf55ab9a60?environmentId=457d4843-26e3-4ebc-a764-27255d2e429d&id=9532d8fd-4159-4b40-97a1-a9c8b398c6e1#http

to the second point: I'm lazy, but I should upgrade

^that link is the redeploy of the successful build, that is in progress, crazy hang time right now, will eventually fail with the error code in the log file

@Error

@DannyDev does switching off the metal builder in the service settings fix this?

trying that right now!

@Medim turned off metal builder and did a redeploy, looks like its gonna hang again, does turning off metal builder work for redeploy or does redeploy deploy exactly like it did the first time(which was with metal builder)

You turn off the metal builder and apply the changes, that would cause a new redeploy.
Redeploying old instances would use the current service settings (not old ones like the first time)

Does it make sense? 😆

Let's see if it will hang on the same step

it worked

seems like something with metal build rn

other guy had the same issue and hopping off metal build worked for him also

because had it on for as long as I can remember without issue and just started failing

Yep, I've shared this issue with the team

are yall gonna create an incident so I can show something to my coworkers as an esxcuse sign off for the night lmao?? or something on the status page?

Doesn't seems too widespread so I don't think an incident will be called 😆

well appreciate the help nontheless!

thanks for unblocking!

back to work I go