Failed introspection with Alchemy / Satsuma subgraph endpoints missing __schema
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 50/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- graphql
- Domain
- documentation
Research direction
Start with the README instructions for graphclient build and review the reported Alchemy/Satsuma failure involving the __schema field. Update the relevant README section to warn that these endpoints do not support introspection, and consider the issue complete when users are informed before following the build instructions.
Written by the indexing model from the issue text.
Description
Issue
After following the full instructions, I got the following error with an Alchemy / Satsuma subgraph while running the graphclient build command. When using an identical subgraph deployed to The Graph instead, everything worked as according to the README instructions. There may be missing features on Alchemy's endpoints causing this. It appears that the issue may be that Alchemy does not support querying the __schema field. Perhaps it doesn't even exists in those endpoints' data.
Suggestion
It would be good to note this in a message in the readme.
As of 2025-10-29 Alchemy subgraphs do not support introspection with graphclient build due to missing support for __schema field queries
Console Error Output
sensitive data redacted
root@fedora:/app/base# bunx graphclient build
[2025-10-28T21:46:00.058Z] INFO GraphClient Cleaning existing artifacts
[2025-10-28T21:46:00.079Z] INFO GraphClient Reading the configuration
[2025-10-28T21:46:00.823Z] INFO GraphClient Generating the unified schema
[2025-10-28T21:46:02.553Z] ERROR GraphClient - subgraph-name Failed to generate the schema for the source "subgraph-name"
Failed to fetch introspection from https://subgraph.satsuma-prod.com/REDACTED/REDACTED/subgraph-name/version/v0.0.1-new
-version/api: TypeError: Cannot read properties of undefined (reading '__schema')
at /app/node_modules/@graphql-mesh/graphql/cjs/index.js:155:36
at process.processTicksAndRejections (node:internal/process/task_queues:103:5)
at async Object.getWithSet (/app/node_modules/@graphql-mesh/store/cjs/index.js:174:38)
at async Promise.allSettled (index 0)
at async GraphQLHandler.getMeshSourceWithoutFederation (/app/node_modules/@graphql-mesh/graphql/cjs/index.js:385:52)
at async GraphQLHandler.getMeshSource (/app/node_modules/@graphql-mesh/graphql/cjs/index.js:250:28)
at async /app/node_modules/@graphql-mesh/runtime/cjs/get-mesh.js:89:28
at async Promise.allSettled (index 0)
at async getMesh (/app/node_modules/@graphql-mesh/runtime/cjs/get-mesh.js:84:5)
at async Object.handler (/app/node_modules/@graphql-mesh/cli/cjs/index.js:308:53)
[2025-10-28T21:46:02.553Z] ERROR GraphClient Error: Schemas couldn't be generated successfully. Check for the logs by running Mesh with DEBUG=1
environmental variable to get more verbose output.
at getMesh (/app/node_modules/@graphql-mesh/runtime/cjs/get-mesh.js:123:15)
at process.processTicksAndRejections (node:internal/process/task_queues:103:5)
at async Object.handler (/app/node_modules/@graphql-mesh/cli/cjs/index.js:308:53)
- Dominant language
- TypeScript
- Stars
- 185
- Forks
- 49
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from graphprotocol/graph-client
-
Difficulty 1/5 Under an hour Newbie friendliness 85/100
graphprotocol/graph-client#1029 ·
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
graphprotocol/graph-client#1031 · 4 comments ·
-
[Bug] The order data source under sources tab in .graphclientrc.yml affects the query resultPossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 3/5 1-2 days Newbie friendliness 55/100
graphprotocol/graph-client#1001 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 28/100
graphprotocol/graph-client#957 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
graphprotocol/graph-client#940 · 6 comments · 1 reaction ·
All issues in graphprotocol/graph-client
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
AOSSIE-Org/DebateAI#611 ·
Maintainers usually reply within 3 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
openzim/mwoffliner#2933 ·
Maintainers usually reply within 1 day
-
Use the README category name for website links and submissionsPossibly taken @dajiaohuang claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
birobirobiro/awesome-shadcn-ui#647 ·
Maintainers usually reply within 2 days
-
Twake Drive picker: closePicker() never destroys the intent (stop() is on the promise returned by start(), not by create())Possibly taken @chibenwa claimed this today. Openclaude
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
linagora/twake-calendar-frontend#1498 · 1 comment ·
Maintainers usually reply within 1 day
-
check:passed streams:add
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day