I’m seeing quite a few deployments failing with an error similar to this:
Failed due to unhealthy allocations - not rolling back to stable job version 23 as current job has same specification and deploying as v24
I’m also seeing some strange behaviour with scaling. I have created 3 volumes across 3 regions (ams, fra, cdg), but when I set
fly scale count 3, I only see 1 instance being run and the others don’t show at all:
ID VERSION REGION DESIRED STATUS HEALTH CHECKS RESTARTS CREATED 9d223a09 24 ams run running 0 26m46s ago
is this potentially related to the same issue? Thanks.