issue has propped up again in ORD and deploys are failing 
. Support ticket is a P2 even when you select it is stopping me from using fly.io. Yet again status page is all green
we have support, I have a ticket opened since yesterday got a single response 4hrs later and now I am back to square one stuck.
2 days and we still can’t deploy. While being on a support plan
In general, you should be able to fork the volume in this situation, since the problem is temporary congestion on that single underlying physical host machine.
(The error message could probably be more clear that it is a highly localized anomaly.)
If all you ever wanted was a single Machine with a volume, however, then the Fly.io platform probably wasn’t that great of a fit all along, although it’s unfortunate that this was the way to discover such things, 
.
(This is all just my personal opinion, by the way. I don’t work at Fly.io.)
Reusing a year-old, mostly unrelated thread is probably muddying the waters overall. OP’s problem was with the release command and tokens, which doesn’t appear to be that similar to this week’s new posts…
2 Likes
Yesterday I also received the error:
--> Build Summary: ()
--> Building image done
WARN failed to finish build in graphql: ensure depot builder failed, please try again (status 401): {"message":"Unauthorized"}
image: registry.fly.io/strapi-staging:deployment-01KF0JKKXWAB95PG6M8097P9Y4
image size: 260 MB
Watch your deployment at https://fly.io/apps/strapi-staging/monitoring
Error: failed to set release status to 'running': failed to update release (status 401): {"message":"Unauthorized"}
Error: Process completed with exit code 1.
But just now restarted and it successfully finished