Incomplete Metadata from QlikSense API for Duplicated Apps

[prharish]

Problem Description

We are experiencing an issue where QlikSense apps created using the "Duplicate" feature return incomplete or empty metadata when accessed through the QlikSense Engine Service (port 4747) via WebSocket connections.

How We Access QlikSense

We connect to QlikSense Enterprise using:

• Connection Method: WebSocket (wss://)
• Port: 4747 (Qlik Sense Engine Service)
• Protocol: HTTPS/WebSocket
• Purpose: Extracting app metadata including load scripts, variables, sheets, and object definitions

Specific Issues Observed

1. Empty Variables Metadata

When retrieving app variables from duplicated apps:

Expected Structure:

{
  "qItems": [
    {
      "qId": "variable-id",
      "qName": "VariableName",
      "qDefinition": "expression"
    }
  ]
}

Actual Response from Duplicated Apps:

{}

Impact: Cannot retrieve any variable definitions from the app, even though variables are visible in the QlikSense Hub UI.

2. Empty Load Script

When retrieving the load script from duplicated apps:

Expected: The complete load script with data loading logic, transformations, and connection strings.

Actual Response from Duplicated Apps:

{}

Impact: Without the load script, we cannot understand the app's data sources, transformations, or data flow logic.

3. Missing Object Metadata

When retrieving sheets, dimensions, measures, and master objects, we observe:

• Empty or missing JSON responses
• Incomplete object definitions
• Missing visualization metadata

Even though these objects are visible and functional in the QlikSense Hub.

Environment

• QlikSense Enterprise on Windows (QSEoW) — November 2025, version 14.254.6
• Accessing via QMC / browser only

More Details : 

When using the built-in Duplicate function on a QlikSense app, certain copies (in my case the 10th duplicate, named TestApp2Copy(10)) return completely empty metadata when accessed via the QlikSense API.

Specifically, all extracted data files are empty or missing:

• variables.json contains only {} — no qItems array
• loadScript.json contains only {}
• sheets/, dimensions/, measures/, masterObjects/, stories/, bookmarks/ folders are all empty

The original app (TestApp2Copy) and all other copies (TestApp2Copy(1) through TestApp2Copy(9), and copies named without parentheses like TestApp2Copy1, TestApp2Copy2, etc.) return full, valid metadata correctly. And If I renamed the App name to TestApp2Copy10  then that will work with the new name (OR) even if I created another AppTestApp2Copy10 then Both TestApp2Copy(10) and TestApp2Copy10 will works

Steps to Reproduce

1. Export any working App  eg: TestApp2Copy.qvf
2. Import it as Duplicate   First Try to name TestApp2Copy(1) , TestApp2Copy(2), ....etc
3. The extracted apps will get fails using the API
4. Try to rename it to TestApp2Copy1, TestApp2Copy2  it will work, else create another apps TestApp2Copy1, TestApp2Copy2..... Then Both TestApp2CopyN and (TestApp2Copy(N) will work.

Observed Behavior

The API returns {} for GetVariables and GetScript for the affected app, even though the app appears fully functional in the QlikSense Hub UI (sheets are visible, data loads correctly).

Renaming the app (removing the (N) suffix) and re-accessing via API returns valid data, suggesting the issue is specific to how the server handles metadata retrieval for apps with parenthesized suffixes at certain indices.

Expected Behavior

The API should return full metadata (variables, load script, sheets, etc.) for all duplicated apps regardless of the copy number or naming convention.

Questions

1. Is there a known issue with the QlikSense Duplicate function returning incomplete metadata for apps at certain copy indices?
2. Is there a server-side fix or workaround other than exporting to .qvf and re-importing?
3. Does this correlate with any known behavior related to the (N) naming pattern used by the Duplicate function?

[prharish]

Could anyone help me on this ?

[prharish]

Is this due to the migration of Qliksense from of my November 2025  ---->  May 2026 ?