During Release "Error server returned a non-200 status code: 504"

Questions / Help
22

We are still getting tons of these 504s while deploying from a CI. We have the staging and production versions of the same app in different organisations so the order is:

  1. deploy staging with the staging org deploy token
  2. do a flyctl auth logout as we were getting lots of errors otherwise
  3. deploy production with the production org deploy token

Step number 3 fails most of the times with a 504. Anyone else experiencing this? It’s becoming very problematic for our release lifecycle.

1 Like