Qlik Cloud Automation API response missing Content-Length header

[jxp]

I'm using Power Automate to call a Qlik Cloud Automation execution endpoint. This worked fine until recently (last successful run: April 29, 2026). As of May 14, 2026, it fails with HTTP 411: "Content-Length for source file is missing or invalid."

The Qlik automation itself works correctly (verified via browser and Power Automate custom connector). The issue is that the HTTP response from Qlik's `/actions/execute` endpoint no longer includes a `Content-Length` header.

Response headers from Qlik (captured via Chrome DevTools):

access-control-allow-origin: *
content-encoding: gzip
content-type: application/json
date: Thu, 14 May 2026 22:35:59 GMT
strict-transport-security: max-age=15724800; includeSubDomains
vary: Accept-Encoding
x-job-guid: 40198e7b-125f-4a2c-bd98-f2d7b786c44f

No `Content-Length` and no `Transfer-Encoding` header. The response is gzip-encoded with no declared size.

Questions:

1. Was there a recent infrastructure change to how Qlik Cloud serves automation execution responses? (This worked on April 29 and broke by May 14.)
2. Is there a way to force the `/actions/execute` endpoint to return a `Content-Length` header?
3. Is there a way to disable gzip compression on automation responses (e.g., via request headers or automation settings)?
4. Are there plans to address this, as it breaks integrations with services that require `Content-Length` (e.g., SharePoint/OneDrive)?

Thank You!

[Shai_E]

Hi @jxp 

These are questions for a support case.

Best Regards

[hakana]

Could you please check if the change is on the Qlik Automate side or if it's SharePoint, adding this as a requirement

https://community.powerplatform.com/forums/thread/details/?commentid=14e39efd-1d4a-f111-bec6-7c1e520...

[jxp · Accepted solution]

Thanks everyone! Yes, this is most likely new requirement on Power Automate side, not Qlik. 

For the future readers, there are two way how to overcome it...

• Solution 1 (my personal):

Keep using the Upload file from URL as a trigger, pass some unique ID in parameters, set the next action Run After property also to Has failed. This way the Upload file from URL triggers the HTTP GET, fails with the response, but the flow continues. The response from Qlik then can be passed back to MS e.g, using SharePoint list with some ID provided from Upload file from URL parameter. Good thing is, Upload file from URL waits for the response even if it then fails, so there is no timing issue.

• Solution 2 as per the link from hakana above, but honestly, i did not test it.