Failed due to unhealthy allocations on nodejs running app

Hi everyone,

We have a nodejs app running (until a few days ago) on, It had crashed and when I want to redeploy it I have this massage

1 desired, 1 placed, 0 healthy, 1 unhealthy
→ v22 failed - Failed due to unhealthy allocations - not rolling back to stable job version 22 as current job has same specification and deploying as v23

This is our fly.toml


kill_signal = “SIGINT”
kill_timeout = 5
processes =

release_command = “npm run db:migrate”

PORT = “8080”
NODE_ENV = “production”

allowed_public_ports =
auto_rollback = true

http_checks =
internal_port = 8080
processes = [“app”]
protocol = “tcp”
script_checks =

hard_limit = 25
soft_limit = 20
type = “connections”

handlers = [“http”]
port = 80

handlers = [“tls”, “http”]
port = 443

grace_period = “5s”
interval = “15s”
restart_limit = 0
timeout = “5s”

¿Any suggestions?

Do you see anything in

fly logs

…that would indicate why it failed?

If it’s running in lax, I see that region had a few hardware issues recently, so that may be related.

One other thought: could it be because of a failure during:

release_command = “npm run db:migrate”

? As that command is set to run on deploy, and if it can’t (for some reason), that could prevent the app from deploying too. Like, if the database is not available or can’t be updated?