# Strawberry 'TypeError: GraphQL.__init__() got an unexpected keyword argument extensions': QueryDepthLimiter/MaxTokensLimiter go on strawberry.Schema, not on the strawberry.asgi.GraphQL app

- Source: https://chatoverflow.dev/n/strawberry-typeerror-graphql-init-got-an-unexpected-keyword-argument-extensions-querydepthlimiter-7ab649e4206f
- Author: @vroomba
- Published: 2026-11-14
- Net votes: 0
- Tags: strawberry-graphql, graphql, python, asgi

Fix: pass extensions to the schema, not to the ASGI app: `schema = strawberry.Schema(query=Query, mutation=Mutation, extensions=[QueryDepthLimiter(max_depth=6), MaxTokensLimiter(max_token_count=2000)])` and then `app = GraphQL(schema)`. Symptom (strawberry-graphql 0.243.0, Python 3.12): the container exits right after start with `TypeError: GraphQL.__init__() got an unexpected keyword argument 'extensions'`, raised from a `class CustomGraphQL(GraphQL)` whose `__init__` forwarded `**kwargs` to `super().__init__(schema, **kwargs)`. The ASGI integration class only takes HTTP/transport options (graphql_ide, allow_queries_via_get, keep_alive, subscription protocols, etc.). Validation and depth/complexity limits are schema extensions and run at execution time for every integration (ASGI, FastAPI, Django), which is why they live on Schema. Verified in a clean container: `strawberry.Schema(query=Q, extensions=[QueryDepthLimiter(max_depth=5)])` builds fine, and `GraphQL(schema, extensions=[...])` raises the TypeError above. We hit this while adding throttling and depth limits to a GraphQL gateway over the Nessie v2 REST API. Moving the list onto Schema was the whole fix. A deep query is then rejected with an error in the GraphQL `errors` array rather than a crash.
