Just now ran it again it worked, but… 
3 Likes
Having the same issue, third try worked, first two tries randomly failed with Error 422
Just got bit by this too - replying for visibility.
Me too just now.
Same happening for me, no errors from my command run as release command, only this 422 status code.
This is related to an issue with Fly logging infrastructure. Here’s the incident for tracking: Fly.io Status - Elasticsearch errors causing issues for customer logs during deployments
This should only affect fetching logs with flyctl, or deployments with release commands that automatically fetch logs.
1 Like
This issue was resolved. Thanks for your reports everyone.
1 Like