👀 See Sanity in action: Watch product demo now →

Migration API Mutation Error: Request Body Exceeds Limit of 4000000 Bytes

11 replies
Last updated: May 9, 2022
We are migrating all of our data from the old CMS to Sanity via API mutations, and some of the resources are throwing errors “Request body exceeds limit of 4000000 bytes”. Most of those are portable text. Any workaround suggestions?
May 6, 2022, 2:39 PM
Ooooh, tricky. 😅
May 6, 2022, 2:40 PM
I wonder if dedicated support could help you bypass them maybe?
May 6, 2022, 2:40 PM
You could try doing it in multiple smaller passes, but this could be tricky depending on what your schema looks like.
May 6, 2022, 2:42 PM
Can block content / portable text even be broken down?
May 6, 2022, 2:45 PM
I already reduced the batch sizes to 1 entry per request, so I am not sure how I would go about it. I guess patching the partable text array would be an option, but it’s a super complex migration logic, which iterates through a gazillion nodes, migrates assets et al.
May 6, 2022, 2:45 PM
With transactions, I am not sure how to safely split the transaction to ensure that item references do not throw errors.
May 6, 2022, 2:46 PM
Maybe json-ld import is better for this? 4mb is a lot though
May 6, 2022, 2:47 PM
What’s a json-ld import?
May 6, 2022, 2:51 PM
I have a ton of markdown that needs to be transformed into portable text, not sure what json-ld has to do with it
May 6, 2022, 2:52 PM
Looks like there are some long raw svgs, will try to optimize that part
May 6, 2022, 3:07 PM
Ok. It’s me stupid. There was no clean up happening after the page was imported, so it kept adding transactions to a stack for each new page, until it reached the limit, which now that I think about it is huge. False alarm.
May 9, 2022, 11:50 AM

Sanity.io – build remarkable experiences at scale

Sanity is a customizable solution that treats content as data to power your digital business. Free to get started, and pay-as-you-go on all plans.