422: Unprocessable Entity

1

On build I get the error 422: Unprocessable Entity

←[2mYou can detach the terminal anytime without stopping the deployment←[0m
←[31mError←[0m 1 error occurred:
        * 422: Unprocessable Entity
2

Sorry about that. The release is going through but the deployment monitor is throwing an error. Should be fixed shortly.

3

This is fixed now.

1 Like
4

I am getting 504 errors now :frowning:

5

Oh no! What are the steps to get a 504?

6

I get this v30 is being deployed ←[1A←[2K1 desired, 1 placed, 0 healthy, 0 unhealthy [health checks: 1 total] ←[1A←[2K1 desired, 1 placed, 0 healthy, 0 unhealthy [health checks: 1 total, 1 passing] ←[1A←[2K1 desired, 2 placed, 0 healthy, 0 unhealthy [restarts: 1] ←[1A←[2K1 desired, 2 placed, 0 healthy, 0 unhealthy [restarts: 1] ←[1A←[2K1 desired, 2 placed, 0 healthy, 0 unhealthy [restarts: 1] [health checks: 1 total] ←[1A←[2K1 desired, 2 placed, 0 healthy, 0 unhealthy [restarts: 1] [health checks: 1 total] ←[1A←[2K1 desired, 2 placed, 0 healthy, 0 unhealthy [restarts: 1] [health checks: 2 total, 1 passing] ←[1A←[2K1 desired, 2 placed, 0 healthy, 0 unhealthy [restarts: 1] [health checks: 2 total, 1 passing] ←[1A←[2K1 desired, 2 placed, 0 healthy, 0 unhealthy [restarts: 1] [health checks: 2 total, 2 passing] ←[2mv30 running - Deployment is running pending automatic promotion ←[0m←[31mError←[0m 1 error occurred: * server returned a non-200 status code: 504

7

Thanks. Does it happen every time? That error is a timeout and I’m curious if there’s an unrelated network issue causing trouble.

8

not every time it is sometimes

9

There is seemingly no pattern it can work then it breaks then it works like 5 tries later

10

We’ll take a look and try to reproduce. Could you DM me your app name?

11

The 504 is related to some work we’re doing on the API. It should be resolved by tomorrow.

12

@heppcat this should be fixed now. We were migrating our GraphQL API between backend services using Apollo Federation. During the migration (which is done now) we were making significantly more api calls between the gateway and the backend which was causing some requests to timeout.