Introspection query fails

[rickbijkerk]

most basic hive router setup with our graphql schema isnt working

config:

# router.config.yaml
supergraph:
  source: file
  path: ./supergraph.graphql

(best to contact me directly through dm's and ill be able to share some info on our schema with you )

[ardatan]

Have you tested it with another supergraph like here?
https://the-guild.dev/graphql/hive/docs/router/getting-started#get-a-sample-schema
Or is it failing only with your supergraph?
Also could you check Network tab in your browser to see how Router responds via HTTP?

[rickbijkerk]

Yes other supergraph do work it's just our supergraph that isnt working.

network tab on the graphql request

let me know if you need more info

[ardatan]

Could you run the router with LOG_LEVEL=trace environment variable, make it fail and share the log?

[rickbijkerk]

{"timestamp":"2025-12-09T09:01:58.604634Z","level":"TRACE","fields":{"message":"Found normalized GraphQL operation in cache (operation name=Some(\"IntrospectionQuery\")): query IntrospectionQuery "},"target":"hive_router::pipeline::normalize"}
{"timestamp":"2025-12-09T09:01:58.604652Z","level":"TRACE","fields":{"message":"sucessfully collected variables from incoming request: None"},"target":"hive_router::pipeline::coerce_variables"}

thread 'worker:3' (983456) panicked at lib/executor/src/introspection/resolve.rs:402:58:
called `Option::unwrap()` on a `None` value

is this sufficient? if not let me know if you need more

[ardatan]

That's very helpful! Thanks! Do you run the binary directly or use the Docker image?

[rickbijkerk]

right now i just ran the binary directly to test if it would work for our graph

[ardatan]

I did some small changes to learn more about the issue;
Could you download the alpha release (released binaries from https://github.com/graphql-hive/router/actions/runs/20058123964?pr=606) and try with it?

hive_router_linux_amd64
hive_router_linux_arm64
hive_router_macos_amd64
hive_router_macos_arm64

[rickbijkerk]

we're getting somewhere, previous error disappeared, now im seeing

/graphql response seems to be empty

[ardatan]

Hmm I am not sure if it is empty. Because;

• Decorated type deeper than introspection query. error comes from GraphiQL while parsing the introspection result.
• Also it has 200 with some response size.

I have a few questions;

• Could you check the response on the right view for the entry you shared in the screenshot in Network tab?
• Also do you have multi dimensional arrays in your schema like [[[[SomeItem]]]]?
• I guess you ran the router with LOG_LEVEL=trace so do you have any logs like Type '{}' not found in the schema unexpectedly during introspection

[rickbijkerk]

ah you're right the response was simply that big that it didnt load in the first second i was looking at it, the response is there.

the only occurence of '[[' i could find in my schema is
directive @transport(kind: String!, subgraph: String!, location: String!, headers: [[String]]) repeatable on SCHEMA

and indeed now that you mention it i do see an issue reported in the logging

{"timestamp":"2025-12-09T11:53:17.721382Z","level":"TRACE","fields":{"message":"Type 'join__Graph' not found in the schema unexpectedly during introspection"},"target":"hive_router_plan_executor::introspection::resolve"}