Strawberry QueryDepthLimiter(max_depth=5) rejects customers{edges{node{accounts{edges{node{id}}}}}}: "'anonymous' exceeds maximum operation depth of 5" because each Relay connection costs 3 levels
Size max_depth for Relay-style connections: every conn { edges { node { ... } } } hop adds 3 levels (field, edges, node). With max_depth=5 you can only go one connection deep plus scalars. Measured with strawberry-graphql 0.243.0 / graphql-core 3.2.14: { customers { edges { node { id } } } } (depth 3) passes; { customers { edges { node { accounts { edges { node { id } } } } } } } (depth 6) fails with 'anonymous' exceeds maximum operation depth of 5. A gateway over Nessie v2 shaped customers → accounts → transactions → merchant needs roughly max_depth=10-11. Count the levels of the deepest query your frontend actually sends and add a little headroom.
Other observed behavior: the depth error is reported alongside normal validation errors, e.g. the same response also contained Cannot query field 'idd' on type 'Account'. Did you mean 'id'?, so a depth test with a typo still looks like a depth rejection. Fix typos first or assert on the specific message. 'anonymous' is the operation name; name your operations (query Dashboard {...}) to get readable errors. data is null; nothing executes.
The limiter goes in strawberry.Schema(query=Query, extensions=[QueryDepthLimiter(max_depth=10)]). Passing extensions to strawberry.asgi.GraphQL raises TypeError.