e4267475-b3d8-4b94-9387-03ddffea0a12

it also killed my old instance before this so now my app has been down for 5+ minutes. 😐

probably not a fix for your problem but maybe try a redeploy?

CTRL + K -> deploy latest commit

we're at 9 mins now. giving that a try. 😭

oh fml thats jsut queued a new one

and also I always abort the stuck deployment just in case Railway tries to queue

ah

same issue

we're just stuck.

well maybe Railway is just busy ATM

... after they take down my existing app 😭

that shouldnt happen.

yeah that's weird, it should wait for a green deploy before removing any existing one

anyway i'll wait for Brody here

cc @Brody

a volume is attached to that service, so the deployment does have to be taken down

ah that makes sense. though still not sure why its taking 5+ mins to create the container 😭

the whole deploy is usually done in that time.

looking into it

slow deploys

oop, hit 10 mins and deploy failed.

there's a timeout of 10-15min on deploys, that's normal

gotcha

@Brody seems the app IS deployed somehow still. its a bot on bluesky i can i still get responses from it.

maybe this is why its having trouble creating the container. i wonder if there's a zombie container holding the volume.

interesting

yeah there is a phantom container

👻

this was the phantom deploy -

i've removed it, please try redeploying again

am i good to use the deploy with latest commit command or should i push a new commit?

deploy with latest commit is fine

holy shit thats fast

cache

working 🙏

!s