Thinkmill / Thinkmill/keystatic
[GraphQL] The request payload cannot be larger than 45MB
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2.4k
- Forks
- 159
- Avg merge
- 21h 41m
- Merged PRs (30d)
- 2
Description
Hello! On the website where I use Keystatic Cloud, I'm trying to create a grid with GIFs. Everything has been going well—it creates the grid perfectly, and the images are added as they should. But I've reached a point where it won't let me publish updates anymore, and I'm getting this error message:
[GraphQL] The request payload cannot be larger than 45MB
I don’t quite understand the error; the website’s YAML file is less than 1.5KB, and this happens not only when uploading a new image but also when I try to delete one, which doesn’t make much sense.
The POST request to https://api.keystatic.cloud/v1/github/graphql takes 15 seconds, returns a 200 OK status, and nothing appears in the browser console; the only error is the one that appears at the top of the website on a couple of specific pages. I haven't found any mention of this limit in the documentation, nor have I found anyone else experiencing the same issue.
Contributor guide
No contributing guide indexed for this repository
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 by reproducing the failure on the affected pages and inspect the POST request to https://api.keystatic.cloud/v1/github/graphql, comparing uploads, deletions, and successful updates. Trace how the request payload is assembled and determine why it reaches the 45MB limit despite the small YAML file. Done means the affected updates no longer fail, or the limit and its cause are clearly documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, typescript
- Domain
- api
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100