Notifications
Clear all
Topic starter
I'm encountering an unusual issue where my HTTP nodes sometimes execute successfully, and other times I receive a 413 error (Payload too large). I currently have two nodes exhibiting this behavior.
The first node sends some text to Flowise and gets a response back. The amount of text isn't substantial, approximately 8 lines if I paste it here. If I save and then reload the workflow, and run the entire workflow, the node executes without any problems. However, if I attempt to run just that specific node, it fails.
The second node is making a call to an Airtable API for comments, and I've only been testing with the text "Test API comment". This node will only execute when I run the workflow for the first time after reloading it.
Does anyone have any advice?
Posted : 05/09/2023 1:50 pm
Topic starter
After some additional testing, I've found that executing the entire workflow runs without any problems. However, attempting to run either of these two nodes individually leads to a "Payload too large" error.
This seems like an unusual bug. Are there any potential solutions for this?
Posted : 05/09/2023 2:15 pm
Hi, I am sorry you’re having trouble. I am not quite sure in which context the error appears for you so I don’t know if it’s thrown by Flowise or by callin.io here (or perhaps by a webserver somewhere along the way).
On the callin.io side of things you can increase the max payload size by setting the CALLINIO_PAYLOAD_SIZE_MAX environment variable to a higher value than the default of 16 MB. Keep in mind that the total payload exchanged between the callin.io server and your UI is much bigger than just the example data you’re sending in your 2 HTTP Request nodes (as all input and output data for each node and every single item processed in your workflow would have to be transferred).
Posted : 06/09/2023 10:26 am
This thread was automatically closed 90 days following the last response. New replies are no longer permitted.
Posted : 05/12/2023 10:26 am