Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Catch up on the newest Qlik features and improvements: Learn More
cancel
Showing results for 
Search instead for 
Did you mean: 
herard_bertrand
Partner - Creator II
Partner - Creator II

Qlik Automate "Call URL" block: is there a ~1 MB limit on the request body? (502 Bad Gateway)

Hi everyone,

I have a Qlik Automate automation, started from a button in a Qlik Cloud app.
It sends a JSON, built by a measure in the app, to our own web service with a "Call URL" block
(POST, JSON in the body). The web service then generates an Excel file.

It works fine for small selections, but for big ones I get a "502 Bad Gateway", returned very quickly (about 160 ms).

I did tests step by step, measuring the JSON size with Len() in the app:
- about 1,036,600 bytes: OK
- about 1,051,000 bytes: 502
- above that: 502 every time

So the threshold seems to be around 1 MiB (1,048,576 bytes). It doesn't depend on the content:
I removed items one by one until it worked, then sent the last removed item alone, and it went through.

What I checked on the web service side:
- There is no log at all for the failed calls, so the request doesn't seem to reach the service.
- When I send the same kind of JSON directly to the service (through its Swagger page, without Qlik Automate),
it works up to 2.9 MB at least.
- Enabling or disabling "Run asynchronously" doesn't change anything.

My questions:
1. Is there a known size limit on the request body sent by the "Call URL" block (or on a block output / variable
in Qlik Automate)? Or at least, is it documented somewhere?
2. If there is one, is there a recommended workaround (sending a file instead of the body, splitting the call, ...)?

(My guess is a limit on the Qlik side, since the 502 comes back so fast, but I'd be happy to be proven wrong 🙂 )

Thanks in advance!

Labels (2)
0 Replies