Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Search our knowledge base, curated by global Support, for answers ranging from account questions to troubleshooting error messages.
Qlik offers a wide range of channels to assist you in troubleshooting, answering frequently asked questions, and getting in touch with our technical experts. In this article, we guide you through all available avenues to secure your best possible experience.
For details on our terms and conditions, review the Qlik Support Policy.
Index:
We're happy to help! Here's a breakdown of resources for each type of need.
Support | Professional Services (*) | |
Reactively fixes technical issues as well as answers narrowly defined specific questions. Handles administrative issues to keep the product up-to-date and functioning. | Proactively accelerates projects, reduces risk, and achieves optimal configurations. Delivers expert help for training, planning, implementation, and performance improvement. | |
|
|
(*) reach out to your Account Manager or Customer Success Manager
Your first line of support: https://community.qlik.com/
Looking for content? Type your question into our global search bar:
Leverage the enhanced and continuously updated Knowledge Base to find solutions to your questions and best practice guides. Bookmark this page for quick access!
Subscribe to maximize your Qlik experience!
The Support Updates Blog
The Support Updates blog delivers important and useful Qlik Support information about end-of-product support, new service releases, and general support topics. (click)
The Qlik Design Blog
The Design blog is all about product and Qlik solutions, such as scripting, data modelling, visual design, extensions, best practices, and more! (click)
The Product Innovation Blog
By reading the Product Innovation blog, you will learn about what's new across all of the products in our growing Qlik product portfolio. (click)
Q&A with Qlik
Live sessions with Qlik Experts in which we focus on your questions.
Techspert Talks
Techspert Talks is a free webinar to facilitate knowledge sharing held on a monthly basis.
Technical Adoption Workshops
Our in depth, hands-on workshops allow new Qlik Cloud Admins to build alongside Qlik Experts.
Qlik Fix
Qlik Fix is a series of short video with helpful solutions for Qlik customers and partners.
Suggest an idea, and influence the next generation of Qlik features!
Search & Submit Ideas
Ideation Guidelines
Get the full value of the community.
Register a Qlik ID:
Incidents are supported through our Chat, by clicking Chat Now on any Support Page across Qlik Community.
To raise a new issue, all you need to do is chat with us. With this, we can:
Log in to manage and track your active cases in the Case Portal. (click)
Please note: to create a new case, it is easiest to do so via our chat (see above). Our chat will log your case through a series of guided intake questions.
When creating a case, you will be prompted to enter problem type and issue level. Definitions shared below:
Select Account Related for issues with your account, licenses, downloads, or payment.
Select Product Related for technical issues with Qlik products and platforms.
If your issue is account related, you will be asked to select a Priority level:
Select Medium/Low if the system is accessible, but there are some functional limitations that are not critical in the daily operation.
Select High if there are significant impacts on normal work or performance.
Select Urgent if there are major impacts on business-critical work or performance.
If your issue is product related, you will be asked to select a Severity level:
Severity 1: Qlik production software is down or not available, but not because of scheduled maintenance and/or upgrades.
Severity 2: Major functionality is not working in accordance with the technical specifications in documentation or significant performance degradation is experienced so that critical business operations cannot be performed.
Severity 3: Any error that is not Severity 1 Error or Severity 2 Issue. For more information, visit our Qlik Support Policy.
If you require a support case escalation, you have two options:
When other Support Channels are down for maintenance, please contact us via phone for high severity production-down concerns.
A collection of useful links.
Qlik Cloud Status Page
Keep up to date with Qlik Cloud's status.
Support Policy
Review our Service Level Agreements and License Agreements.
Live Chat and Case Portal
Your one stop to contact us.
With the new inclusion of the Get Chart Image block in the Qlik Reporting connector in Qlik Application Automation, you now have more opportunities to notify a group of users with more in-depth data and charts using Slack.
The Get Chart Image block does currently not support base64 conversions of the generated PNG file. This means that it is not yet possible to send images directly to Microsoft Teams or embed them in an HTML email. We are working on improvements to make this possible in a future release.
This article will guide you in sending your first chart image to Slack with Qlik Application Automation.
You can download an example of the automation from this article: Send-chart-image-slack.json
Warning: Whenever the “Get Chart Image” block is to be used, we advise you to only use it with temporary bookmarks or pre-existing persistent bookmarks.
If the condition block outcome evaluates to false:
The information in this article is provided as-is and will be used at your discretion. Depending on the tool(s) used, customization(s), and/or other factors, ongoing support on the solution below may not be provided by Qlik Support.
A Qlik Replicate task with a Salesforce source endpoint may encounter the following task log error on some tables:
[SOURCE_UNLOAD ]E: An DATASET_ERROR error occurred unloading dataset: .<tableName> (custom_endpoint_util.c:1155)
The endpoint server log files (if the logging level is set to TRACE or VERBOSE) will read:
"errorMessage" : "Failure during batch processing: InvalidBatch : Query processing exception: OPERATION_TOO_LARGE: exceeded 100000 distinct who/what's"
The issue is related to user permissions. When a user without the View All Data permission runs a task on activities involving a large number of related records, Salesforce may throw a "Query processing exception: OPERATION_TOO_LARGE: exceeded 100000 distinct who/what's" error, indicating that more than 100,000 distinct who/what's records were queried.
The Salesforce administrator should grant View All Data permission to the affected user's profile. Once this permission is enabled, the task will run successfully without errors.
Qlik Replicate tasks using Oracle as a Source Endpoint fail after installing the Oracle July 2024 patch.
All Qlik Replicate versions older than the 2024.5 SP03 release are affected.
Upgrade to Qlik Replicate 2024.5 SP03 or later once available.
In the meantime, Qlik has made early builds of 2023.5, 2023.11 and 2024.5 available.
Download the early builds here:
2023.5 SP07: https://files.qlik.com/url/qjfazk7fxftjmncu
password: cdesfgb8
2023.11 SP05: https://files.qlik.com/url/ndafzunah2srntqt
password: bl3xrefv
2024.5 SP03: https://files.qlik.com/url/fbfsznjidxt5nzra
password: cygie73l
The Oracle July 2024 patch introduced a change to redo events. Qlik has since provided a fix for Qlik Replicate which parses the redo log correctly.
RECOB-8698
Oracle Database 19c Release Update July 2024 Known Issues
As a general reminder, all changes to the environment such as operating system patches, endpoint and driver patches, etc. should be tested in lower environments before promoting to production.
Executing tasks or modifying tasks (changing owner, renaming an app) in the Qlik Sense Management Console and refreshing the page does not update the correct task status. Issue affects Content Admin and Deployment Admin roles.
The behaviour began after an upgrade of Qlik Sense Enterprise on Windows.
This issue can be mitigated beginning with August 2021 by enabling the QMCCachingSupport Security Rule.
Enable QmcTaskTableCacheDisabled.
To do so:
Upgrade to the latest Service Release and disable the caching functionality:
To do so:
NOTE: Make sure to use lower case when setting values to true or false as capabilities.json file is case sensitive.
Should the issue persist after applying the workaround/fix, contact Qlik Support.
After applying the Oracle July 2024 patch, the following error will be seen when working with compressed tables:
[ASSERTION ]W: A compressed row cannot be parsed for table (oradcdc_parse.c:2640)
The error leads to missing records.
Qlik is actively working on a fix to address the issue caused by the Oracle July 2024 patch. If you have not yet upgraded and plan to, consider waiting until a fix is available for Qlik Replicate. We expect one by the end of week 39.
Only Oracle instances with compressed tables are affected.
If you are uncertain whether or not you are using compressed tables, run the following query:
select owner, table_name, COMPRESSION,COMPRESS_FOR from dba_tables where compression='ENABLED'
If waiting is not an option, please upgrade to Qlik Replicate 2023.11.724 and log a ticket with support if you encounter problems with compressed tables post-upgrade.
Oracle July 2024 Patch with compressed tables. It is being investigated as RECOB-8914 by Qlik.
When a user is deleted, any spaces, apps, scripts, and data connections they own will remain in the tenant without an owner. To prevent orphaned records, reassign ownership of these assets before deleting the user. Source: Reassigning ownership of spaces and resources (Qlik Cloud Documentation)
But even if the app is considered an Orphaned App, the owner can be changed in the Qlik Cloud Analytics Administration Console:
Opening the Table Selection option in the Designer tab of a managed Qlik Replicate server, the following error may be triggered:
Error: SYS-E-HTTPFAIL, SYS-E-UNRECREQPARM, Unrecognized request parameter 'action'.. SYS,GENERAL_EXCEPTION,SYS-E-UNRECREQPARM, Unrecognized request parameter 'action'.,SYS,UNRECOGNIZED_REQUEST_PARAMETER,action
The same may be visible when clicking the Test Connection button in the Qlik Enterprise Manager.
No additional errors are logged in the Qlik Sense Enterprise Manager log files. The issue is predominantly seen after an upgrade.
Restart the Qlik Enterprise Manager service.
The restart clears the browser cache, solves the issue, and prevents it from occurring again on the next load.
After an upgrade of the Qlik Enterprise Manager (to, for example, 2024.5), UI elements in the console did not load correctly.
The authentication token associated with auto Provisioning is about to expire
Or
The authentication token associated with auto Provisioning has expired
The token must be deleted that was created for SCIM Auto-provisioning with Azure.
curl "https://<tenanthostname>/api/v1/api-keys?subType=externalClient" \ -H "Authorization: Bearer <dev-api-key>"
Ensure to replace <tenanthostname>
with your actual tenant hostname and <dev-api-key>
with your generated developer API key. Execute the command in Postman or a similar tool, and make sure to include the API key in the header for authorization.
Once you have obtained the key ID from the output, copy it for later use in the deletion process.
To delete the API key associated with SCIM provisioning, execute the following curl command:
curl "https://<tenanthostname>/api/v1/api-keys/<keyID>" \ -X DELETE \ -H "Authorization: Bearer <dev-api-key>"
<tenanthostname>
with your actual tenant hostname, <keyID>
with the key ID you obtained in step 2, and <dev-api-key>
with your developer API key. Execute this command in Postman or a similar tool, and ensure that the API key is included in the header for authorization.By following these steps, you can successfully delete the token created for SCIM Auto-provisioning with Azure.
The information in this article is provided as-is and is to be used at your own discretion. Depending on the tool(s) used, customization(s), and/or other factors ongoing support on the solution below may not be provided by Qlik Support.
The token was not deleted when the SCIM Auto-Provisioning was disabled or completely removed.
Using the qlik-cli it is possible to import a list of users to a tenant from a csv file.
It will be then possible to assign roles, entitlements and space permissions to the users before they log in to the tenant.
Here's a possible example of how to do that.
Name,Email
Mick Case,Mick.Case@example.com
Davide Bironi,Davide.Bironi@example.com
Kenny Handsley,Kenny.Handsley@example.com
Leigh Kersriver,Leigh.Kersriver@example.com
Gerry Vain,Gerry.Vain@example.com
Tommy Ioni,Tommy.Ioni@example.com
Terence Attendant,Terence.Attendant@example.com
John Oughborne,John.Oughborne@example.com
William Guard,William.Guard@example.com
Renato Padovano,Renato.Padovano@example.com
# Import the csv file as an array of objects
$csv = Import-Csv -Path userlist.csv
# Initialize a counter for the subject
$counter = 1
# Loop through each object in the array
foreach ($row in $csv) {
# Generate the subject using the counter
$subject = "ExampleSubject" + $counter
# Execute the qlik-cli command with the column values and the subject
qlik user create --name $row.Name --email $row.Email --subject $subject
# Increment the counter
$counter++
}
#!/bin/bash
# Get the number of lines in the csv file
lines=$(wc -l < userlist.csv)
# Loop from the second line to the last line (skipping the header row)
for ((i=2; i<=lines; i++))
do
# Get the name and email values from the ith line using cut
name=$(cut -d, -f1 userlist.csv | sed -n "${i}p")
email=$(cut -d, -f2 userlist.csv | sed -n "${i}p")
# Generate the subject using the counter
subject="ExampleSubject$counter"
# Execute the qlik-cli command with the column values and the subject
qlik user create --name "$name" --email "$email" --subject "$subject"
# Increment the counter
((counter++))
done
NOTE: users will be created with a temporary SubjectId like "ExampleSubject1", "ExampleSubject2", and so so on. After the first login, users will get a proper SubjectId.
Roles, entitlements and space permissions will follow the users to the new subject.
Alternatives ways of adding users via scripts might be achieved via the an /api/v1/users CALL with the POST method and a payload like:
PAYLOAD:
{
"email": "name@example.com",
"name": "First Lastname",
"subject": "SubjectXYZ"
}
The information and the files in this article are provided as-is and will be used at your discretion. Depending on the tool(s) used, customization(s), and/or other factors, ongoing support on the solution below may not be provided by Qlik Support.
In a tenant, the following options are enabled in the Settings area of the Management Console:
However, when a user is assigned a professional service, the Shared Space Creator, Private Analytics Content Creator, and Data Services Contributor roles are not immediately assigned.
This is working as designed.
Professional entitlement users will receive the new roles automatically after they log in to the tenant for the first time.
Studio is starting with the incorrect JDK even though it's specifically set in JAVA_HOME and the <Studio Home>\Talend-Studio-win-x86_64.ini file.
Please edit and update the -vm option contained within the startup shortcut with correct JDK.
If Studio is launched with a startup shortcut, it may contain a -vm option pointing to a different JDK(old JDK) than the correct one which is already set in the ini file or JAVA_HOME variable.
setting-up-java_home-for windows
When using Talend Studio, you may encounter the following error while attempting to open a remote project or apply a patch update:
javax.net.ssl.SSLHandshakeException: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target
This error typically arises due to a missing or untrusted certificate in the Java keystore required to establish a secure connection. This article provides step-by-step instructions to resolve this issue in two common scenarios:
Verify Java Version:
Download and Install the Required CA Certificate:
Import the CA Certificate into Java Keystore:
Locate the cacerts file (typically at <JAVA_HOME>/jre/lib/security/cacerts).
Open a command prompt or terminal and navigate to the directory containing your cacerts file.
Use the keytool command to import the certificate:
keytool -import -alias <alias_name> -file <path_to_certificate_file> -keystore <path_to_your_jdk>/jre/lib/security/cacerts
Replace:
When prompted, enter the keystore password (default is changeit).
Verify the Import:
List the certificates in the cacerts file using:
keytool -list -v -keystore <path_to_your_jdk>/jre/lib/security/cacerts
Ensure the imported certificate appears in the list.
Verify Java Version:
Download Required CA Certificate:
Import the Certificate into Java Keystore:
Configure Talend Studio to Use the Updated Keystore:
Add the following JVM argument to your Talend Studio talend.ini file:
-Djavax.net.ssl.trustStore=<path_to_your_jdk>/jre/lib/security/cacerts
Replace <path_to_your_jdk> with the path to your JDK installation.
If you are operating behind a corporate proxy, you may need to import the proxy server's SSL certificate into your Java keystore. Similarly, any specific corporate firewall rules that could be blocking connections to Talend Cloud should be reviewed and configured to allow necessary traffic.
Data inconsistencies can be observed when replicating an SQL view from SQL to Hadoop. The column in the underlying table is of the FLOAT data type.
Example:
The source has 5 decimals, while the target has more than 10.
SQL Source value of the float datatype = 11.14008 T
Hadoop Target value of the float datatype = 11.1400800000000001
Qlik Replicate does not add precision explicitly. The behavior is caused by the nature of the FLOAT datatype; no configuration steps or workarounds exist to change the datatype's behavior.
FLOAT is, by definition, not a precise data type.
For additional reading on FLOAT, see, for example:
RECOB-8880
Publishing an app in a Qlik Sense Enterprise on Windows (client-managed) environment may fail with the error:
Quota is exceeded
Reduce the size of files attached to the app. Alternatively, delete unnecessary files you have attached to it.
You can review what files you have attached to the app from the Qlik Sense Management Console:
The maximum file size of an individual file attached to an app is 50 MB, while the maximum total size of files attached to the app (including image files uploaded to the media library) is 200 MB.
See Attaching data files and adding the data to the app for details.
Attaching data files and adding the data to the app | Qlik Sense on Windows Help
It is finally here: The first public iteration of the Log Analysis app. Built with love by Customer First and Support.
"With great power comes great responsibility."
Before you get started, a few notes from the author(s):
Chapters:
01:23 - Log Collector
02:28 - Qlik Sense Services
04:17 - How to load data into the app
05:42 - Troubleshooting poor response times
08:03 - Repository Service Log Level
08:35 - Transactions sheet
12:44 - Troubleshooting Engine crashes
14:00 - Engine Log Level
14:47 - QIX Performance sheets
17:50 - General Log Investigation
20:28 - Where to download the app
20:58 - Q&A: Can you see a log message timeline?
21:38 - Q&A: Is this app supported?
21:51 - Q&A: What apps are there for Cloud?
22:25 - Q&A: Are logs collected from all nodes?
22:45 - Q&A: Where is the latest version?
23:12 - Q&A: Are there NPrinting templates?
23:40 - Q&A: Where to download Qlik Sense Desktop?
24:20 - Q&A: Are log from Archived folder collected?
25:53 - Q&A: User app activity logging?
26:07 - Q&A: How to lower log file size?
26:42 - Q&A: How does the QRS communicate?
28:14 - Q&A: Can this identify a problem chart?
28:52 - Q&A: Will this app be in-product?
29:28 - Q&A: Do you have to use Desktop?
Qlik Sense Enterprise on Windows (all modern versions post-Nov 2019)
*It is best used in an isolated environment or via Qlik Sense Desktop. It can be very RAM and CPU intensive.
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.
Optimizing Performance for Qlik Sense Enterprise - Qlik Community - 1858594
This guide provides a step-by-step process for installing and configuring the Oracle 21c Instant Client for use with Qlik Replicate. Note that Qlik Replicate should already be installed before proceeding.
For more information, Setting up Qlik Replicate on Linux, a comprehensive list of supported Linux platforms and prerequisites, refer to the Supported Linux Platforms section in the User Guide.
curl -O https://download.oracle.com/otn_software/linux/instantclient/2115000/oracle-instantclient-basic-21.15.0.0.0-1.el8.x86_64.rpm
curl -O https://download.oracle.com/otn_software/linux/instantclient/2115000/oracle-instantclient-sqlplus-21.15.0.0.0-1.el8.x86_64.rpm
To verify the connectivity between the Oracle client and server, you can use SQLPlus by running the following commands:
sudo su - attunity
cd /opt/attunity/replicate/bin
source arep_login.sh
sqlplus scott/tiger@192.168.33.210:1521/orcl
In this example, scott/tiger@192.168.33.210:1521/orcl represents the Oracle connection string
This document explains the differences between Talend license levels, and describes important steps that must be completed before lowering your license level with Talend products. Talend offers three different license levels: listed from advanced to basic, they are Master Data Management, Management, and Data Integration/ESB. Talend projects, Jobs, and components are not compatible across each of the licenses available, so if you lower a license without first performing the proper steps, the potential for critical problems is high. This document will help you successfully lower your license level with Talend products.
This article is relating to downgrading Talend Data Fabric license to Talend Real-Time Big Data Platform. The difference between the licenses is that the MDM features/user type is removed for RTBDP licenses. If you have a Talend Data Fabric license with any MDM projects, you'll need to proceed with the following steps below.
|
|
|
The license used in Talend Administration Center enables an administrator to create and administer projects and users of different types. You can see what licenses you have available in Talend Administration Center by navigating to the Menu tree > Settings > Licenses.
The example used here will be downgrading from Master Data Management to Data Management. If you are downgrading from Master Data Management or Data Management to Data Integration/ESB, the concept will be the same
You must create new projects inside of TAC with the project type of Data Management, or to the level of the license you are downgrading to. To complete this part, you must log into TAC and locate Projects under the Menu tree. Since you are not able to change the project type on an existing project, you may duplicate a project, then select the correct project type. If you are connecting to GIT, verify that the settings and URL are correct under the Advanced Settings after duplicating or creating a new project.
After the new project with the correct license level is created, you will not be able to see the project available in Studio until you provide the users with permissions. Inside of TAC, you will need to locate Project Authorizations under the Menu tree. Here you must choose the new project and provide the users with the desired permissions on the right side. In the Rights column, you can choose to give either Read Only or Read/Write by choosing the icon with the person and pencil. If you have any groups, you will need to choose the tab at the top center Authorization by User/Group to make sure the groups also have the proper permissions.
Log into TAC, navigate to the Menu tree, and locate Users. You must lower the users from MDM to DM (or the desired license level) on the right-side panel of each user that is selected. If applicable, you should verify that their GIT user is correct.
During this process, you should keep one user at your current license level until the end of the downgrading project, preferably the admin user.
If you are unable to change the user type, you may not have the proper permissions or the user may still be logged in.
To verify if the user is logged in, check the Users page of Talend Administration Center. You can see which users are logged into the Talend Studio, Talend Data Preparation, and Talend Administration Center. Log them out if needed.
Data Preparation and Talend Data Stewardship will not be covered in depth, but if the user is a Data Preparation or TDS user be sure to check the Data Preparation User box and select their desired roles.
To begin this portion, log in as the user at your current license level, as discussed in the Users section.
When you start up your Studio, be sure to choose the existing projects that have your current license level. If you are doing remote, you can verify the user that you are logging in with, so you know you are entering the correct projects and have proper permissions.
Once you have logged in to your current project, you will need to begin exporting your Jobs into a specified location.
To export a Job:
You will then want to log into the new project, which should be empty and have the license level you will be downgrading to. Once you have logged in to that project, you will need to import the jobs you previously exported.
To import a Job:
Once you have imported your Jobs, you will want to test them in the new project and verify that the components work and are not a part of the higher-level license that you plan to downgrade from. To confirm that your components function properly, review the Component Reference Guide
If you have any schedules, it would be a best practice to verify the Jobs run on the schedulers and any other unique designs you may have implemented.
Once you have verified that your Jobs run successfully on the new license platform, request the downgraded license from your Customer Success Manager.
This article aims to explain how SQL server T-log cleans up works when Microsoft replication\publication is enabled on the database.
When the Qlik Replicate task first time runs to capture CDC, Qlik Replicate will create a publication on the database with required articles. As part of this publication log reader agent job also will be created and this job will continuously run to mark replicated transactions on the database.
Apart from the Replicate process, there will be a transactional log backup job that will run every 15 mins or 30 mins depends on source team policy. As part of this log backup job, all the transactions will be backup up to that point in time and truncate all replicated and committed transactions from T-log.
Assume, there is a scheduled t-log backup job going to run at 10 am, and the replicate task is reading transaction log with 5 mins latency, there is a high possibility that the backup job will remove the transaction(s) from a transactional log which hasn't read by the Qlik Replicate. In this scenario, the Qlik Replicate task will be failed with a missing LSN error.
To prevent such kinds of issues Qlik Replicate implemented an option to hold T-log for a couple of mins without truncating based on the below setting:
Qlik Replicate creates an internal table called attrep_truncation_safeguard on the source database and always runs two update queries (2 update queries for each Qlik Replicate task running on the database) without commit (called Latch Lock A and B), only when you enable Start transactions in the database setting on source SQL endpoint. Qlik Replicate will update the time on these queries every 5 mins by default and we can control time by using an Option called "Apply TLOG truncation prevention policy every (seconds): ".
Here are the screenshots to explain how to check these open transactions on the database.
Qlik Enterprise Manager (QEM) analytics show the error:
could not open file base/16394/16500: No such file or directory.
Qlik Enterprise Manager analytics data is stored in the Postgres database from your Repository connection. The data is stored as tables and retrieved by QEM. This error refers to the table's Postgres base file being missing.
The base files indicated in the error message will need to be restored either through:
Consult your Postgres DBA for the procedures.
If no backups are available, then the Repository connection needs to be initialized to recreate all the tables. All previous Analytics data will be deleted and recreated.
Postgres upgrades and maintenance may cause missing base files. Best practices include stopping the Qlik Enterprise Manager collector before maintenance and always backing up your database to ensure changes can be reverted if undesired behavior occurs.
After an upgrade of Qlik Replicate (2022.5 to 2023.11), tasks using a PostgreSQL source see truncations for the varchar column when running a full load.
The following is logged in the source_unload logging component:
[SOURCE_UNLOAD ]V: Value for (varChar column) was truncated. bind type: -8, data len: 14 (14, after truncation: -2), bind len: 0, statement:
Add the Internal Parameter unboundedVarcharMaxSize on the Postgres Aurora source endpoint and set it to 8000.
If you are using Logstream setup, please add unboundedVarcharMaxSize on the Postgres Aurora source endpoint in both the Logstream Parent task and child task.
To resolve the issue:
The Internal Parameter has unexpectedly changed between Qlik Replicate 2022.5 and 2023.11. This only affected Postgres Aurora.
While unboundedVarcharMaxSize had a default value of 8000 in 2022.5, it is now set to -1 for Postgres Aurora by default.
RECOB-8644