When exporting data from a Qlik Sense App, the Printing Service creates a temporary file which is stored in a temporary folder. 

Exported XLSX files are stored in: C:\ProgramData\Qlik\Sense\Repository\TempContent.
The folder is in the node where the repository is installed.

The data is automatically deleted after 10 minutes by the Engine. This is not currently a configurable property. 

Related Content

How to change how long temporary excel files are stored by the QlikView server 

Qlik offers a variety of coursework and training materials to help you adopt Qlik products faster and maximize their capabilities. Choose from Free online Courses, Self-paced Learning, Instructor-Led training, and custom Application Training. 

Our existing offers can be found on Qlik's Training Site.

Content:

• To Access Free Qlik Training
• To Access Self-paced Training
• To Access Instructor-led Qlik Training

To Access Free Qlik Training

1. Head to our Free Training landing page 
2. Click Access All Free Training 
3. Log in with your Qlik ID
   
   
   
   
4. And start browsing!
   
   You can filter for Free training in the Price drop-down.
   
   

To Access Self-paced Training

1. Head to our Qlik Learning landing page 
2. Log in with your Qlik ID
   
   
   
   
3. Click Self-Paced Learning
   
   
   
   
4. Click Visit the Qlik Continuous Classroom
   
   
   
   
5. And start browsing! You can start by clicking Try it Free or Subscribe to a Learning Package that best suits your needs.
   

   Tip! Once you get started, you can track your training progress and browse for more content in your personal Learning Portal.

To Access Instructor-led Qlik Training

1. Head to our Instructor-led Training Overview  
2. Click View All Instructor-led Classes 
3. Log in with your Qlik ID
   
   
   
   
4. Filter based on various properties, such as user roles, products, and time zones. Then choose your class by clicking Schedule & Pricing
   
   
   
   
5. Choose your schedule and whether you are booking for an individual (Register Myself) or a group (Register Group)
   
   
   
   
6. Continue with your purchase.

Qlik Replicate does not support Oracle on Delphix. 

It has not been tested nor certified with Oracle on Delphix. The use of the untested combination can lead to unexpected behavior.

Environment:

Qlik Replicate 
Oracle Delphix

Previewing or publishing a Qlik NPrinting report fails with the message:

Some of row's cells lay outside column

Resolution

Remove any merged cells from the report.

Cause 

This is caused by the 'Aspose' library Qlik NPrinting uses for generating reports.

Related Content

Exception when deleting table column: class com.aspose.slides.PptxEditException: Some of column’s cells lay outside column | Aspose.com

Environment

• NPrinting May 2022 and above
• QlikView May 2022 and above

Qlik Sense data files (.QVF) may contain sensitive organizational data.  As such, even though Qlik Technical Support has a very strict Non-Disclosure Agreement, it may be desired to  scrambled specific data before submitting apps Qlik Sense support for investigation.

For the currently available method in Qlik Sense Enterprise for Windows, see Scramble Sensitive Data In Qlik Sense Enterprise for Windows.

Data can be scrambled in two ways:

• Using Qlik Application Automation
• Using a predefined Excel sheet

Before providing the scrambled application to Qlik Support, please check that you can still reproduce the issue within the scrambled application.

Using Qlik Application Automation

The attached automation_scramble_Support.json automation creates a copy of your app before scrambling the data. 

Requirements:

• the app must be stored in a Shared Space (not a Personal Space or Managed Space)
• the user running the automation must have access to the Shared Space
• the tenant must have the Automation feature enabled; scrambling data using Qlik Application Automation is not available in Qlik Sense Business or Qlik Cloud Analytics Standard

To scramble your data using the automation:

1. Download automation_scramble_Support.json
2. Open your Qlik Cloud hub
3. Create a new Automation
   
   
   
   
4. Select Blank automation
5. Right-click the blank automation workspace and click Upload Workspace (see How to import and export automations)
6. Select and upload automation_scramble_Support.json
   
7. Configure the automation:
   1. Click the Get App Information block
   2. Add your app's ID in App Id
      
      
      
      
8. Click Run to run the automation
9. A copy of your app named Scrambled_YourAppName is created

Using a predefined Excel sheet

If Automations are not enabled, or you do not have the correct subscription model, use the attached Qlik Script and Excel file to scramble the data. 

To scramble data using an excel file and a Qlik script:

1. Duplicate the app in the Cloud hub
2. Review the app and work out the list of fields (and related tables) you want to scramble. Replace the contents in the metadata file scramble.xlsx with the list.
3. Upload both the edited scramble.xlsx and scramble.qvs (attached to this article) to a space in your tenant
4. On the duplicated app, paste the following script into the app script editor before any other script statement, including the SET variable statements (which should have been removed or commented out). Substitute the file names stored in the Binary data source location accordingly.

   Binary;
   $(Include=lib://NAMEOFSPACE:DataFiles/scramble.qvs);
   
   CALL Scramble('lib://NAMEOFSPACE:DataFiles/scramble.xlsx');
   
   Exit Script;

5. Reload the duplicated app and review the result
6. Export the app from the hub
   
   

Related Content:

Idea / Feature Request - Data Masking 
Alternative method using APIs and the DevHub: Data Scrambling in Qlik Sense 
Scramble Sensitive Data In Qlik Sense Enterprise for Windows
To access the examples, visit the community post or download it from here. 

Environment

Qlik Cloud 

There has always been a noticeable gap in Qlik Replicate, where users had no means of importing just an endpoint into Qlik Replicate. This article provides a workaround to that limitation.

1. To start creating an endpoint, it is advisable to prototype something the product generates.
   
   Create a dummy task with a dummy endpoint (source or target) which resembles the endpoint you wish to import. This task or endpoint does not have to be perfectly filled out. See example below: 
   
   
   
   
2. Once the dummy task has been set up, export the task. See Exporting tasks.
   
   
3. Open the resulting JSON file. See Editing an exported (json) file. 
   
   
4. You will only need the following definitions from the task JSON payload:
   
   The "cmd.replication_definition"."databases" group and a "_version" member:
   
   

   {
   	"cmd.replication_definition":	{
   		"databases":	[{
   		...
   			}]
   	},
   	"_version":	{
   		...
   	}
   }

5.  Create the JSON definitions of the endpoint following the example below. This will be the endpoint you import. 
   
   

   Verify that your endpoint name is correct.  
   
   

   You may want to skip entering the password and add it later through the user interface. Inputting the password in the JSON is in plain text.

   {
   	"cmd.replication_definition":	{
   		"databases":	[{
   				"name":	"DB2z_Source",
   				"description":	"",
   				"role":	"SOURCE",
   				"is_licensed":	true,
   				"type_id":	"DB2ZOS_NATIVE_COMPONENT_TYPE",
   				"db_settings":	{
   					"$type":	"Db2zosSettings",
   					"additionalConnectionProperties":	"MaryHad=aLittleLamb",
   					"username":	"dimae",
   					"databaseAlias":	"DBALIAS",
   					"server":	"lpardns.mydomain.com",
   					"port":	5035,
   					"databaseName":	"LOCATION",
   					"CCSIDMapping":	"234,ibm-p100-2345",
   					"ifi306SpName":	"R4Z_UDF_ALL_NEW"
   				},
   				"override_properties":	{
   				}
   			}]
   	},
   	"_version":	{
   		"version":	"2023.5.0.213",
   		"version_major":	2023,
   		"version_minor":	5,
   		"version_revision":	213
   	}
   }

6. Save this content as a .JSON file. We recommend the /data/imports folder to make the import command simpler, but any folder and drive your user has access to can be used.
   
   
7. Import the definitions into the Qlik Replicate server.
   
   You can do so using either:
   • Qlik Enterprise Manager API
   • Qlik Enterprise Manager
   • Qlik Replicate UI, 
   • repctl CLI  command (on Windows):
     

     repctl importrepository json_file=NAMEOFFILE.JSON folder_name=DRIVE:\FOLDER

        

Related Content

Editing an exported (json) file
ImportAll | Enterprise Manager API
Exporting and importing tasks
Importing tasks

Environment

• Qlik Replicate
• Qlik Enterprise Manager

The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.

This article gives an overview of the Splunk Connector in Qlik Application Automation.
The Splunk connector has been created with the following use cases in mind:

• Being able to perform searches to a Splunk instance
• Inserting new events into Splunk using the HTTP Event Collector

Connecting the Splunk connector

The Splunk connector makes use of basic authentication. When connecting the connector, you will be prompted with the following popup screen:

Hostname: The hostname or IP address of the Splunk instance. Exclude the http(s):// part and the port number of the URL.
Username: The username you use to login to Splunk
Password: The password you use to login to Splunk
Use SSL: Select whether the management service of Splunk makes use of SSL. Default yes.
Management port: The port on which the management service of Splunk is running. Default is 8089. Providing no value will omit the port from the final URL.

Performing a search on Splunk

To perform searches using the Splunk connector it is possible to perform a synchronous search as well as an asynchronous search. The synchronous search has a timeout of 50 seconds, with the asynchronous search it is possible to have a longer window before the automation will timeout.

Synchronous Search

The synchronous search can be done using the Synchronous Search block. In the Search Query block you will have to provide a splunk search query.

Asynchronous Search

The asynchronous search block can be manually done using the block Asynchronous Search block. Then perform polling using the Get Search block using the returned Search ID. When finished, results can be obtained using the Get Results From Search block.

Alternatively it is possible to use the block Do Asynchronous Search and get Results. This block will perform the polling, only a search query has to be provided to obtain a list of results.

Sending data into Splunk

The other use of the Splunk connector is to send data into Splunk by making use of the HTTP Event Collector. An example usecase for this would be to send reload logs of a Qlik Sense app into Splunk.
To do this we will first have to create an HTTP Event Collector on the Splunk side.

To do this in Splunk go to Splunk in the web browser and go to Settings > Data > Data Inputs.
On this page you will see Http Event Collector. Press the Add new button.

Provide a name for the token and go to the next page. Select indexes to which this token can write. Click on Review and Submit. You will be given a token that you need to configure on the block.

In Qlik Application Automation make use of the Send Event block. For the inputs, enter the HEC token value. Provide the port for the HTTP event collector. This can be obtained from the Splunk HTTP Event Collector page when clicking on the Global Settings button. You can also find whether SSL is enabled for the HTTP Event Collector, select this value for the Hec_Use_Ssl parameter. Next, provide the index to which you're writing your events and provide a source string.
For data, you can map JSON message in the Event parameter.

The following example will perform a reload and send the reload log to Splunk:

In Splunk it is then possible to view the logs of the reload:

The information in this article is provided as-is and to be used at own discretion. Depending on tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.

This article is intended to get started with the Microsoft Outlook 365 connector in Qlik Application Automation.

Authentication and Authorization

To authenticate with Microsoft Outlook 365 you create a new connection. The connector makes use of OAuth2 for authentication and authorization purposes. You will be prompted with a popup screen to consent a list of permissions for Qlik Application Automation to use. The Oauth scopes that are requested are:

• Mail.Send
• User.Read
• Offline_access

Sending Email with the Microsoft Outlook 365 connector

The scope of this connector has been limited to only sending emails. Currently, we do not enable sending email attachments and are looking to provide this functionality in the future. The suggested approach is to upload files to a different platform, e.g. Onedrive or Dropbox and create a sharing link that can be included in the email body.

The following parameters are available on the Send Email block:

• To: A comma separated list of recipients;
• CC: A comma separated list of recipients to which the email should be copied;
• BCC: A comma separated list of recipients to which the email should be blind copied;
• Subject: A title for your email;
• Type: Choose between plain text email or HTML;
• Body: The content of your email. You can use HTML for your email if chosen as the type.

Generating a report and sending an email with the report

As we do not currently support email attachments, we need to first generate a sharing link in Onedrive or an alternative file sharing service. The following automation shows how to generate a report from a Qlik Sense app, upload the report to Microsoft Onedrive, create a sharing link and send out an email with the sharing link in the body. This automation is also attached as JSON in the attachment to this post.

Environment:

Qlik Application Automation 

After an upgrade to Qlik Sense Enterprise on Windows May 2023 patch 3 or later, REST connections fail with the following error: 

"WITH CONNECTION" is not allowed. To allow "WITH CONNECTION", select Allow "WITH CONNECTION" in the connector settings.

The Allow WITH CONNECTION option is not exposed in the REST Connector GUI and cannot be changed.

Qlik Sense Enterprise on Windows August 2023 and later are not affected.

Resolution

To resolve the issue, upgrade to August 2023.

To manually mitigate the issue in the May release branch, replace the  qsdfw_qsefw_qlikview.qliksourceconfig file. Qlik is investigating a solution which does not require manual intervention.

Backup the affected file before continuing with the workaround. When taking the backup, do not keep the backed up file in the same folder. (see end notes)

1. On each Qlik Sense Server node, navigate to: C:\Program Files\Common Files\Qlik\Custom Data\QvRestConnector\
2. Locate qsdfw_qsefw_qlikview.qliksourceconfig
3. Replace qsdfw_qsefw_qlikview.qliksourceconfig with the file attached to this article. 
4. This resolves the issue. 
   
   Subscribe to this article or monitor the release notes for information on an automated fix.
   
   

   This change must be done on all nodes and schedulers.

End notes:

The folder C:\Program Files\Common Files\Qlik\Custom Data\QvRestConnector can only contain one qliksourceconfig file with correct name: qsdfw_qsefw_qlikview.qliksourceconfig

If there are two qliksourceconfig files (even with different names, such as a backup), the first one in alphabetical order will be chosen.

Cause 

QB-20735

Environment

Qlik Sense Enterprise on Windows May 2023 Patch 3 and later 

Does not affect August 2023 and later releases.

Internal Investigation ID(s) 

QB-20735

The Qlik Community is a great resource where all Qlikkies can connect, collaborate and share with their peers, Qlik support engineers, Qlik product management, and Qlik experts!

Since multiple forums are available for each product, community users can post discussions in the most relevant area. Both new and experienced Qlik product users help others learn new tips, share information and provide solutions by replying to discussions. Qlik product managers, Qlik support engineers, Qlik product and services experts as well as Qlik community administrators are moderating all of the forums and blogs. Look for the headset icon to identify Qlik Support responses and the star to designate other Qlik employee responses.

What types of questions should be asked in the Qlik Community?

Search first before posting. Chances are someone else has already posted your question and answer.  If the search does not result in an answer to your question, continue with posting on the Qlik Community. For step by step instructions on posting a question, check out this post.  Any kind of question can be asked on the Qlik Community!

The Community is an excellent resource for asking how-to, scripting, app development and best practice questions. Some examples of questions include but are not limited to:

• How do I connect using a specific connector?
• How do I use a certain function?
• My syntax is not working as expected, what am I doing wrong?
• What kind of visualization works best for this scenario?
• How do I format a number?
• What can I do to improve data load times?
• What is the approach for creating my data model?

Note:  Qlik Community pages, Qlik Help documents, and Qlik public knowledge articles are all regularly indexed by the major search services like Google.  Be sure to append the product name when searching to retrieve specific results regarding Qlik (ex: Qlik, Qlik Sense, QlikView, NPrinting, etc).  Qlik Community results as well as results from Qlik.com, Qlik Help and Qlik Support Portal display.   

What information should I include when posting to the Qlik Community?

The more information the better! Depending on the question, more details may be required to get the conversation flowing. Try to provide as much detail as possible and don't be surprised if peers or other product experts may ask for more information. A solid post should include:

• A detailed description/ask that includes examples
• Provide screenshots to illustrate the issue
• A sample file that users can test with (examples:  .qvf, .qvw, .qvd)
• Code snippets 
• Error messages
• Do not include any sensitive data! Files uploaded to the community will be publicly available.  

Once the question has been posted, make sure to set up notifications so you do not miss when others respond to and like your post. If a response is received that answers the question or solves the issue, be sure to mark the answer as correct by clicking 'Accept as Solution'. This will mark the post as solved and other Qlikkies will gravitate towards this post as it as a possible solution for their issue. Multiple responses can be accepted as a solution so make sure to select all that apply.

How can I participate in this great Community?

It's easy! Create a Qlik Community login and start surfing the forums. Add your thoughts and ideas to any post, let others know you've experienced the same behavior, or like any resolution that has helped you answer a question. Be kind, encouraging and offer any insight you can! Don't be afraid to post a question as others probably have the same one. For more information on using the Qlik Community, start here!  Once you get started, navigate to our popular blogs and subscribe.  Join a group.  There so much you can learn and share when you are connected to the Qlik Community.  

Thank you for being apart of this wonderful Community! Happy Qlikking!

The following error may occur when reloading data from Ms Excel: “Error: Too many columns in data source (16326) but the limit is 10000."

Resolution

Defect QB-22272 reported to R&D

This was an intentional change introduced in Qlik Cloud but was obviously set as a default limit for Qlik Sense Enterprise for windows as well. 

Information provided on this defect is given as is at the time of documenting. For up to date information, please review the most recent Release Notes, or contact support with the ID QB-22272 for reference.

Workaround:

As workaround, please add this parameter "MaxColumnsInDataSource=0" in "settings.ini" file
1. Stop Qlik Sense Engine service
2. Edit "settings.ini" file from C:\ProgramData\Qlik\Sense\Engine
3. MaxColumnsInDataSource=0 and save "settings.ini" file
4. Restart Qlik Sense Engine service and test

Fix Version:

R&D is planning to turn back as it was before the latest release but I can't predict the version in which a fix will be available.

Cause

Product Defect ID: QB-22272

Environment

• Qlik Sense Enterprise May 2023 and above
• Qlik Sense Cloud

Qlik Replicate can be licensed using RepCtl. For instructions on how to license Qlik Replicate using the standard user interface, see Registering a license.

To register a license on Windows:

1. Convert the current text format license to JSON file format
   
   Example license.json file:
   

   {
        "cmd.license":
   
                 {
   
                      "license_type": "EVALUATION_LICENSE",
                      "licensed_to": "QLIK CUSTOMER",
                      "licensed_by": "Attunity US",
                      "serial_no": "60035964",
                      "expiration_date": "2023-12-01",
                      "hosts": "xxx.xxxx",
                      "source_types": "oracle",
                      "target_types": "target",
                      "features": "yyyy",
                      "version": "2023.11",
                      "issue_date": "2023-10-31",
                      "checksum": "xxxxx-xxxxx-xxxxx-xxxxx"
                  }
   }

   
   
2. Place the JSON format license file (license.json created in step 1) in the Qlik Replicate data/imports folder
   
   Example: C:\Program Files\Attunity\Replicate\data\imports\license.json
   
   
3. Open a Windows Command Prompt as administrator
   
   
4. In the command line, change to the <Installation_folder>\bin directory
   
   Example:
   
   cd "C:\Program Files\Attunity\Replicate\bin"
   
   
5. Run the following command:
   
   repctl importlicense license_file=license
   
   
   
   
6. To confirm the registered license or simply view any currently registered license, run the following command:
   
   repctl getlicense   --help
                

To register a license on Linux:

3. Convert the current text format license to JSON file format
   
   Example license.json file:
   

   {
        "cmd.license":
   
                 {
   
                      "license_type": "EVALUATION_LICENSE",
                      "licensed_to": "QLIK CUSTOMER",
                      "licensed_by": "Attunity US",
                      "serial_no": "60035964",
                      "expiration_date": "2023-12-01",
                      "hosts": "xxx.xxxx",
                      "source_types": "oracle",
                      "target_types": "target",
                      "features": "yyyy",
                      "version": "2023.11",
                      "issue_date": "2023-10-31",
                      "checksum": "xxxxx-xxxxx-xxxxx-xxxxx"
                  }
   }

4. Place the JSON format license file (license.json created in step 1) in the Qlik Replicate data/imports folder.
   
   Example:
   
   /opt/attunity/replicate/data/imports/
5. Change ownership of the license.json file:
   
   chown attunity:attunity /opt/attunity/replicate/data/imports/license.json
   
   
6. Run the below commands from the installation bin folder:
   
   cd /opt/attunity/replicate/bin/
   
   source /opt/attunity/replicate/bin/arep_login.sh
   
   ./repctl importlicense license_file=license
   
   
7. o confirm the registered license or simply view any currently registered license, run the following command:
   
   ./repctl getlicense --help

The Qlik Compose monitoring window takes a long time to load.

This is likely caused by old task entries not being purged from the project's ProjectRepoRuntime.sqlite file. 

ProjectRepoRuntime.sqlite is located in <Instation_folder>\data\projects\PROJECT_NAME
Example (default): C:\Program Files\Qlik\Compose\data\projects\YOUR_PROJECT_NAME              

Resolution 

Upgrade to Qlik Compose 2022.5.0-sp16 (2022.5.1177) or any later version.

After the upgrade, note:

1. The UI performance improvements may not be noticeable immediately, as Qlik Compose deletes a set amount of 500 ghost reference records from ProjectRepoRuntime.sqlite at the end of each successful task completion. Depending on the number of entries that need to be cleaned from ProjectRepoRuntime.sqlite, it can take multiple days before real improvement is seen.
2. Once the UI performance stabilizes, Qlik recommends compressing the ProjectRepoRuntime.sqlite file using a third-party tool such as DB Browser for SQLite.

   It is essential to stop the Qlik Compose service and back up the project folder before compacting the file. Please contact support if any assistance is needed. 

Fixed version

2022.5.0-sp16 (2022.5.1177) and higher

Cause

Recob-7766

Information provided on this defect is given as is at the time of documentation. For up-to-date information, please review the most recent Release Notes with RECOB- 7766 for reference.

While using Databricks Lakehouse (Delta) as a target endpoint, it would be highly beneficial for users to have the option to write data to multiple databases within a single target endpoint connection.

Some specific business use cases involve managing more than 30 databases under a single catalogue. Creating over 30 separate target endpoint connections in Qlik Replicate to handle these databases is a big challenge.

In this article, we will explain the solutions to how we can manage multiple databases within a single connection. The same approach can be used in other common databases, including Databricks (Cloud Storage), Microsoft SQL Server, PostgreSQL, and other similar databases.

Resolution

Changing the Target table schema is the equivalent of changing the specified database name in the endpoint settings.

How to manipulate multiple databases within single connection

In the endpoint definition, specify the "Database" name, this is the default database. In our screenshot example, the default database is named "APACDB".

We may use "schema" to identify the non-default database name, which will write different tables of data to different databases within a single connection.

There are two options, Table level, and Global level:

1. In Table Settings (see Table Settings for details):
   1. Open General
   2. Select Table Schema
2. In Global Rules (see Defining global rules for details):
   1. Click New rule
   2. Go to Transformation
   3. Rename schema 
      
      Define a rule which database should be used for the given table(s). For example, apply a global transformation rule to rename schemas from %.% to $AR_M_SOURCE_SCHEMA:
      
      
      

Environment

Qlik Replicate  all versions
Databricks Lakehouse (Delta) all versions
Databricks (Cloud Storage) all versions

Internal Investigation ID(s)

Support case #00122351

The QlikView server creates a last document state or session recovery bookmark ($LASTKNOWNSTATE) when a QlikView document is closed from the Full Browser Client. This allows work to be resumed, even after the session has been terminated. Sometimes, this session or state needs to be cleared.

Symptoms:

A QlikView document does not open and is stuck in:

Resolution:

The last known document state may be attempting to call an invalid state or object created by the user the last time the document was closed.

To clear this, the end-user needs to click the Remove Last Document State button visible in the View Details menu accessible from a link below the document listed on the AccessPoint.
 

Note that clearing the last document state does not mean the session is reset. If the user is still within an active session and they close and re-open the document, the previous session is resumed. This is not the last document state.

The last document state is a bookmark applied at the end of a session.

For a more detailed description, see Session Recovery in QlikView: How to enable it and how it works.

Qlik Sense works normally, but a huge quantity Repository logs is generated. These following  messages are continuously repeated (not necessarily both of them are present).

In System logs:

INFO SERVERNODE System.Repository.Repository.Core.Repository.Common.ModelRepository`1[[Repository.Domain.Model.UserDirectorySettings, Repository.Domain, Version=xx.xx.x.0, Culture=neutral, PublicKeyToken=...]] 
..... Database object has newer timestamp than object being modified; ....
.... ERROR SERVERNODE System.Repository.Repository.Core.Repository.Common.TransactionUtility 
..... Error when committing 

In User Management logs:

WARN SERVERNODE UserManagement.Repository.Repository.Users.SyncUsersWorker ........  
Conflict when trying to do database operation; retrying... at Repository.Core.Repository.Common.AbstractModelRepository.CheckConflicts(IRepositoryObject persistedItem, DateTime itemModifiedDate)↵

The quantity of messages generated is very high and several GB of memory can be occupied in disk in few hours.

Environment

• Qlik Sense until February 2021 Patch 6.

Resolution

In order to avoid a complete filling of the disk, it is necessary to restart the node where the problem occurs. Generally, this  resolves the issue.

To avoid this problem, we have introduced an improvement in the latest Qlik Sense releases that avoids potential conflicts. This improvement is present in Qlik Sense February 2021 Patch 6 and in Qlik Sense May 2021 SR1 or higher releases. An upgrade is recommended to ultimately fix the problem.

Cause

The problem  is due to an incorrect synchronization between the Database and one of the nodes.

Internal Investigation ID(s)

SHEND-509