Fly deploy hangs on release_command

Been having this issue all day thinking it was something wrong with my migration command. But I’ve since tired out the following and it still hangs:

==> Creating release
--> release v138 created

--> You can detach the terminal anytime without stopping the deployment
==> Release command detected: exit 1

--> This release will not be available until the release command succeeds.
Running release task (pending)... 🌍 ```

It should immediately exit and fail the deploy, no?


app = "rtg-staging"
kill_signal = "SIGINT"
kill_timeout = 5
processes = []

release_command = "exit 1"
#release_command = "npx prisma db seed"
#release_command = "npx prisma migrate reset --force"
#strategy = "immediate"

PORT = "8080"
NODE_ENV = "production"

allowed_public_ports = []
auto_rollback = true

internal_port = 8080
processes = ["app"]
protocol = "tcp"
script_checks = []

hard_limit = 250
soft_limit = 200
type = "connections"

grace_period = "5s"
interval = "10s"
method = "get"
path = "/healthcheck"
protocol = "http"
timeout = "2s"
tls_skip_verify = false

force_https = true
handlers = ["http"]
port = 80

handlers = ["tls", "http"]
port = 443

grace_period = "1s"
interval = "15s"
restart_limit = 0
timeout = "2s"

I also have this issue.

1 Like

+1, fwiw

1 Like

Suddenly started working. :slightly_smiling_face:

Is your app in EWR, by any chance?

If so, could well be related to this issue:

It is!

Makes sense. Thanks for the heads up.

What are the odds this capacity issue causes the builder to not get rebooted properly - resulting in having to delete and redeploy?

It is but I dont think the status page showed anything when I descovered my problem.

1 Like

I don’t think Fly’s status page is automated. It may yet be manually updated.

1 Like

@ryanmcgarvey You’re welcome.

I would guess the odds are high. I’d assume anything that requires any new capacity (cpu, ram, disk … etc).

1 Like