# Getting Started with Error Diagnostics in GraphOS Studio

DevFeed: [Getting Started with Error Diagnostics in GraphOS Studio](<https://devfeed.tech/articles/getting-started-with-error-diagnostics-in-graphos-studio-23314.md>)

Original publisher: [Read original article](<https://www.apollographql.com/blog/getting-started-with-error-diagnostics-in-graphos-studio>)

Author: Tim Hingston

Published: 2025-06-24T08:52:53Z

Content type: release

Language: en

Sources: [Apollo Blog](<https://devfeed.tech/sources/apollo-blog.md>)

Topics: [Error Handling](<https://devfeed.tech/topics/error-handling.md>), [Apollo Federation](<https://devfeed.tech/topics/apollo-federation.md>), [GraphOS](<https://devfeed.tech/topics/graphos.md>), [Apollo Connectors](<https://devfeed.tech/topics/apollo-connectors.md>)

Tags: [api](<https://devfeed.tech/tags/api.md>), [apis](<https://devfeed.tech/tags/apis.md>), [apollo](<https://devfeed.tech/tags/apollo.md>), [apollo-connectors](<https://devfeed.tech/tags/apollo-connectors.md>), [apollo-federation](<https://devfeed.tech/tags/apollo-federation.md>), [classification](<https://devfeed.tech/tags/classification.md>), [client](<https://devfeed.tech/tags/client.md>), [diagnostics](<https://devfeed.tech/tags/diagnostics.md>), [error](<https://devfeed.tech/tags/error.md>), [errors](<https://devfeed.tech/tags/errors.md>), [framework](<https://devfeed.tech/tags/framework.md>), [graph](<https://devfeed.tech/tags/graph.md>), [graphos](<https://devfeed.tech/tags/graphos.md>), [graphql](<https://devfeed.tech/tags/graphql.md>), [health](<https://devfeed.tech/tags/health.md>), [http](<https://devfeed.tech/tags/http.md>), [layers](<https://devfeed.tech/tags/layers.md>), [limits](<https://devfeed.tech/tags/limits.md>), [multiple](<https://devfeed.tech/tags/multiple.md>), [studio](<https://devfeed.tech/tags/studio.md>)

## AI overview

Apollo's Extended Error Diagnostics adds a standardized way to classify GraphQL errors in GraphOS, helping teams identify whether an issue came from a client query, schema configuration, or an underlying service. Errors reported to GraphOS include an error code and the associated subgraph or connector name, with Apollo Studio surfacing their type and origin. This addresses a gap in HTTP status codes, which cannot describe multiple errors from federated services in one request. The excerpt notes that GraphQL errors can arise at router, subgraph, or transport layers, and that "errors as data" is not feasible for some router- or transport-layer failures. The supplied text ends mid-sentence while describing response extensions, so further implementation details are unavailable.

## Source excerpt

Apollo Federation makes it easy to orchestrate your backend services into a single unified API. With the recently announced availability of Apollo Connectors, even existing REST APIs can now be easily federated together. Today, we're proud to announce Extended Error Diagnostics, a set of tools designed to help developers quickly identify, classify, and address errors across their graph. HTTP vs.