:alert: Receiving error 413 when creating an assis...
# support
l
Hi Vapi Team... We need some urgent help here. Our calls started failing with HTTP 413 errors, which we had not encountered before. This error indicates that the request entity is too large, and our initial assessment suggests that this may be due to recent changes in the payload sizes or server configurations. Our call is being dropped Details: Issue: HTTP 413 (Payload Too Large) errors Observation: Errors have begun occurring recently; Please let me know if you need further details or access to relevant logs.
m
Yes, dropped call due to 413 (Payload Too Large)
s
@merrells @Leo can you both share your orgIds?
l
I just shared with you in a DM
s
🔵 16:40:22:329 Updated Call "id": "93c229d0-8c81-43b5-ac99-d070517d2ba2", @Leo do you have any specific call ID or complete error response?
l
No, because we are not able to create some calls using the CreateCall API
Does the TwilioCallSid helps?
s
Yes.
l
Just sent
Are there any change related to the max payload size that we should be aware of? (I didn't find anything in the changelogs or in the API doc)
s
No there are not any changes.
@Leo @merrells Switch to using POST /call endpoint instead of /call/phone and check your request body size - it may be too large.
l
Yes, the error we start receiving today indicate that, what is the max size? This started today (we're actively monitoring any issues when we manifest an assistant, and we haven't had this issue before)
Are there any infrastructure/cloudflare changes related to the payload size?
s
@Leo No new changes have been pushed, keep your request body size under 100KB
l
@Shubham Bajaj I think there is an issue in Vapi. The payload we sent that Vapi rejects does not have 100KB
Copy code
Content-Length    97303
We capture another ones that have less than 80KB
d
We are having the same problem since today, a payload problem but we are getting the 413 error.
something surely has changed.
n
@Shubham Bajaj bump here, this is affecting our side as well
message has been deleted
Going here might help as well to get some attention
d
Maybe you didn't change anything but something has changed maybe under the hood for some of your provider. We are getting a cloudflare error from your side.
s
@Damiano Rodriguez @Nomadiction @Leo Looking into it.
l
Same here Damiano. Maybe it's a new cloudflare rule
n
I did a quick test, and the limit seems to be exactly 63.98KB
One extra char and I get the error
Probably 64KB with the headers
s
We are working on it.
s
can you try now
l
Its working
Thank you team!
s
sorry for the disruption.
l
We'll keep monitoring and let you know if we receive more alerts
BTW, thanks @Shubham Bajaj and @sagar