A distributed GraphQL request can fail because one subgraph is unavailable, slow, overloaded, or returning an error. The router must determine how that failure affects the overall response.

Some fields may be nullable and can therefore return partial results while other fields succeed. Non-null constraints can cause errors to propagate through the response tree.

Designing nullability carefully is especially important in distributed GraphQL architectures.