Starting with Monday, August 29th 2022, when the schema generation fails, our GraphQL API returns a 422 HTTP status code instead of a 500 HTTP status code.

Our GraphQL API can currently fail on three scenarios during the generation of your schema:

• Colliding type names
• Colliding field names
• Reserved field names

For more information on how schemas are generated, see the Schema generation section on the GraphQL Content API page.

Before the fix, these scenarios led to an error with a HTTP status code of 500 for any request until the user took specific action to fix the issue. As this is considered an issue on the client side, a HTTP status code of 422 is returned from August 29th.