Error when calling a flow with large files attache

Unknown

Error when calling a flow with large files attache

Unknown

Hi,

We are calling a flow in Decisions with some large files (5Mb), first with 3 files and then 2 files, and receiving the following error:
Maximum request length exceeded.
We have previously had this issue before and we had to add some lines into the web.config files in Web Host and HUI folders, that did the following:
maxRequestLength=2147483647"
maxAllowedContentLength="4294967295"
Do you know why we are still facing request length issues?

Thanks."

Unknown

Hi,

Can you send us the full error message?
If you could recreate and send us a screenshot of the error w/ details as well as the logs again thatd be great.
Thanks.

Unknown

I recreated the issue and the logs are attached:

cid:image001.png@01D35E14.5A667FA0
Our web developers are suppressing the error.

They are sending us the following json model:

In the CaseHistory repeater, they will be sending us 4 objects each with a file attached.
File sizes are: 2Mb, 1Mb, 1Mb and 34Kb
{
sessionid": "NS-2c96bf7e-ea10-11e6-80c2-0050569f1d1a"

Unknown

Hi,
Can you turn off debug level logging and rerun the action that creates this error? I think the logs may have rolled over, which they do with debug enabled, and not captured this error message.
This payload example is that being passed into a Decisions flow that is being called as a REST service?

Unknown

Hi,

I’ve forgotten how to change the logging level, can you remind me?
Yes this example is calling the Decisions flow via a POST REST call.

Unknown

Go to system > administration > system tools > logging
right click and select log level. On the form that opens de-select debug.
You can then re run your test case.

sorry, server log level > enable/disable is the action to take on the logging folder.

Unknown

Hi,

Our web dev’s just came back to say the issue was on their side. They had a max upload limit size set which was under the total size of the 4 files.
Was peculiar why we couldn’t create it with decisions/postman internally.
All is fine.