No on demand app, but a failed to fetch error

[ift_isabelle]

Hi,

I did a little test with ODAG a few weeks ago.
Since that moment we get "Failed to Fetch" errors.
I switched ODAG off again, but the error stays. Anyone any idea how to get rid of the error?

Kind regards,

Isabelle

[Maria_Halley]

@ift_isabelle  Can you explain your issue a bit more? 

[Maria_Halley]

Since this Question is about QlikSense I will move this to the Sense boards

[ift_isabelle]

What kind of information do you need?

The issue is as described, I get an error, while I don’t have an on demand app or even activated on demand app generation in the qmc. Everything started after I did a test with ODAG and dynamic views.

[kleman_emark]

@ift_isabelle, @Maria_Halley 

Hi, we are experiencing the same issue in some of our client's environments.

• Did you please manage to identify a reason and a solution to this issue?

We opened some tickets with Qlik support regarding this particular error, but they were not able to reproduce it yet.

• So far it seems to be linked with third-party extensions, but we did not manage to confirm this presumption yet.

For us this issue appears sometimes in apps where we have some of the Qlik Sense third-party extensions.

• It starts when we try to edit a sheet with the third-party extension object.
• ODAG is turned off, as in your case.

KR,

Tomas

[ift_isabelle]

I opened a case at Qlik support and we are still looking for a solution.
It looks like the Azure Proxy isn't configured properly and is not allowing websockets.
Do you also have some sort of proxy / load balancer in front of it?

[kleman_emark]

No, we do not havy any proxy / load balancer in front. Websockets seemed to be configured all right for us.

We discontinued troubleshooting this issue as it was not reproducible and was very rare.

There is an easy workround - close the error window multiple times in a row(4-5), then the error disappears for some time.

• This makes it only a slight nuissance.
• We will continue troubleshooting only if it occurs more frequently.

[rafaelkaiser]

We have the same problem in a multi-node environment as described above, but the error message only appears on one server when an application is opened. In the meantime, is there a solution to this problem?

[seblabalyerr]

Hi Everyone,

We have the same problem in a multi-node environment too. Is there any solution about this issue?

[morenoju]

I've seen this happening too. Is there any solution?