Intermittent error 1009 “App already open in different mode” on managed app reload after republish (Qlik Cloud)

[leoraed]

Hi everyone,

We are seeing an intermittent reload failure in Qlik Cloud and would like to know if others have hit the same issue and how you solved it.

What we are doing

We refresh analytics apps with a staged → published flow:

1. Reload the app in a shared / staging space
2. Republish that app into a managed space (for end users)
3. Immediately reload the managed copy again

We do this for several visualization apps in parallel per tenant.

The error

Sometimes the managed reload fails with:

EngineAppOpenInDifferentMode

App already open in different mode

(1009 APP ALREADY OPEN IN DIFFERENT MODE)

Important details:

• The failure happens when the Engine tries to open the app, before the load script really runs
• The staged reload usually succeeds
• The republish also succeeds
• Only the following managed reload fails
• It is intermittent (not every app / not every run)
• It seems more likely under concurrency (several Stage 3 chains at once)

Example from a failed reload status:

{

"status": "FAILED",

"errorCode": "EngineAppOpenInDifferentMode",

"errorMessage": "failed to open the document on the engine: ... App already open in different mode (1009 APP ALREADY OPEN IN DIFFERENT MODE)"

}

What we already tested

1. Republish with source data, without managed reload
   After staged reload + republish, the managed app already has the new data (lastReloadTime matches between staged and managed).

2. Trying to force a qNoData vs data conflict with an external Engine/QIX session did not reliably reproduce the same failure.

So for data freshness, the managed reload does not seem required if republish includes source data.

Our current hypothesis

The managed reload right after republish may hit a short Engine race:

• republish/publish session still holding the managed app in a different open mode
• and/or concurrent activity on user-facing managed apps

That would explain the occasional 1009 on the managed reload only.

Questions for the community

1. Has anyone seen 1009 / EngineAppOpenInDifferentMode specifically on managed apps right after republish?
2. Did you solve it by:
   • removing the managed reload and relying on republish with data: "source"?
   • adding a delay / retry after republish?
   • something else?
3. For Qlik Answers: in your experience, is a managed reload still required after republish, or is Answers fine once the app is republished with data?
4. Any official guidance from Qlik on whether managed reloads after republish are recommended or redundant?

Proposed direction (not implemented yet)

Keep:

• staged reload
• republish with explicit data: "source"

Drop (or make optional):

• immediate managed reload

We want to confirm this is safe for others using republish + Answers / Insight Advisor Chat before changing production.

Thanks in advance for any experience or recommendations.

[Miguel_Angel_Baeyens]

1. The error shows when the app tries to open, at the same time, with and without data. I haven't seen this happening on Qlik Cloud, I have seen this happening several times when apps are consumed via mashups. I'd take a look at the Web Developer Tools of the browser to see if the nodata parameter is somewhere in the GET requests, or if there's any other issue popping up that can cause the behavior. In either case, the HAR file of this will be very useful for Support to troubleshoot.

2. As said, it should not happen. If this is an internal Qlik issue, you should log a ticket with Qlik Support.

3. Qlik Answers for the app will always use the data on the application. If the published application already has the data, Qlik Answers will get the latest changes in the data.

4. I always publish the app changes only and reload on the managed with a different data connection than the one used in the Shared space. There's a lot of good ideas worth reviewing about app lifecycle here: https://community.qlik.com/t5/Design/Managing-your-Analytics-lifecycle-in-Qlik-Cloud-Analytics-UPDAT....