Allow disabling batched queries
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 3.5k
- Forks
- 468
- Avg merge
- 3h 9m
- Merged PRs (30d)
- 2
Description
We are trying to disable batched queries using the provided config setting: 'batched_queries' = false,. The app still process all incoming queries, however, seemingly ignoring the setting.
I would expect to be thrown an error, for there to be an error message for each subsequent batched request, or for the additional requests to have been ignored entirely.
Steps to reproduce
- Set
'batched_queries' => falsein theconfig/lighthouse.phpfile - Rebuild containers and/or clear caches as appropriate
- Send the below JSON as the body of a POST request to the graphql endpoint
- Receive a response containing an array of two results instead of denying the request
[
{
"query": "query { batchOne: me { uuid } }"
},
{
"query": "query { batchTwo: user(uuid: \"{UNIQUE_ID}\") { first_name } }"
}
]
Output/Logs

Lighthouse Version
^5.38
Contributor guide
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.
Research direction
Start with config/lighthouse.php and the GraphQL endpoint, then reproduce the issue using the provided batched JSON request with batched_queries set to false. Trace where the setting is read and how batched requests are handled; done means the configured behavior consistently rejects or ignores batched requests rather than returning two results.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, laravel, php
- Domain
- api, backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100