GraphQL is extremely popular but notoriously time consuming to debug: While traditional APIs use HTTP status codes to help you filter which requests returned an error, every GraphQL request returns the same 200 “OK”, so developers have to look through every single request to find if one has errors. Unlike traditional APIs which use a different endpoint for each product function, every GraphQL query reuses the same endpoint (“/graphql”), which makes it tedious to find the GraphQL request you’re looking for when debugging. But not anymore! As part of GraphQL Debug Tools, Automatic Error Detection parses all the GraphQL queries to surface the ones with errors as errors, even though they return a 200 status. Additionally, Mutation Name Visibility now parses out which GraphQL request is for which mutation and surfaces the mutation name front and center in Jam dev tools, making it much easier to skim or search and find the important request to debug.