Skip to main content
Woohoo! Qlik Community has won “Best in Class Community” in the 2024 Khoros Kudos awards!
Announcements
Nov. 20th, Qlik Insider - Lakehouses: Driving the Future of Data & AI - PICK A SESSION
cancel
Showing results for 
Search instead for 
Did you mean: 
manoranjan_d
Specialist
Specialist

404-Error-QlikSense

On first time login, only one api call is getting succeeded while the other calls are getting 400 error. We are currently showing the contents in different frames and so all of them will be loaded at once. Once I refresh the page, I am able to view all the contents.

 

Please let me the root cause and solution for this issue.

Labels (4)
4 Replies
manoranjan_d
Specialist
Specialist
Author

Hi expertise

 

Waiting for your valuable reply for the issue  

NadiaB
Support
Support

Hi @manoranjan_d 

Can you verity the API call you are using is valid and returning a value?

 

How to use Postman to make API calls and use/verify JSON output

https://support.qlik.com/articles/000104686

 

Make sure the API call was properly configured and all the parameters are correct, usually Postman will give a more descriptive error, it is suggested to review the API documentation to verify the method in use is properly set according the definition to the version of the Qlik Sense server you are using.

 

Kind Regards.

 

Don't forget to mark as "Solution Accepted" the comment that resolves the question/issue. #ngm
Øystein_Kolsrud
Employee
Employee

There's a big difference between the codes 404 and 400. 400 is "Bad request" while 404 "Not found". Sounds like there is something wrong with the calls you are doing. Or do you mean you are doing the same api call several times and it only works the first time around?

Levi_Turner
Employee
Employee

As @Øystein_Kolsrud pointed out, a 404 HTTP response is really radically different than a 400. For the 400 issue presenting with multiple iFrames, I suspect this this to be the resolution: https://support.qlik.com/articles/000098524. In brief, by using multiple iFrames you are bursting a series of independent requests at the Qlik Sense Proxy Service (QPS) with the same identity. Lowering this value should resolve your current issue.

Cheers