Good news! We have 2 fixes that should be rolled out in the next day or so that should eliminate these problems.

Hey @Aleks please give it another try whenever you get a chance. This limit issue should be resolved now!

Considering that we had 37k+ lines in our case (5MB+)

@Dan Miller (Cloud Posse) I think he needs to also wait for the next version of atmos that has the new

--upload

functionality

Yes, Erik is exactly right. There are two limits at play here: the Vercel request body limit (4.5MB) for uploading to Atmos Pro, and a separate limit for serverless function processing (Inngest, 256KB). Previously, the serverless processing limit was the bottleneck — the server-side fix we've deployed eliminates that constraint entirely by storing the payload in blob storage and passing only a reference. However, the Vercel 4.5MB upload limit still applies. Since your payload is 5MB+, you'd hit that limit before the request even reaches our code. The Atmos CLI update Erik mentioned strips unused fields before upload, reducing payload size by ~70-75% — which would bring your 5MB payload down to roughly 1.25-1.5MB, well within the Vercel limit. In your case, you'll need both updates