Qlik Sense Enterprise Client-Managed offers a range of Monitoring Applications that come pre-installed with the product.

Qlik Cloud offers the Data Capacity Reporting App for customers on a capacity subscription, and additionally customers can opt to leverage the Qlik Cloud Monitoring apps.

This article provides information on available apps for each platform.

Content:

• Qlik Cloud
• Data Capacity Reporting App
• Access Evaluator for Qlik Cloud
• Answers Analyzer for Qlik Cloud
• App Analyzer for Qlik Cloud
• Automation Analyzer for Qlik Cloud
• Entitlement Analyzer for Qlik Cloud
• Reload Analyzer for Qlik Cloud
• Report Analyzer for Qlik Cloud
• How to automate the Qlik Cloud Monitoring Apps
• Other Qlik Cloud Monitoring Apps
• OEM Dashboard for Qlik Cloud
• Monitoring Apps for Qlik Sense Enterprise on Windows
• Operations Monitor and License Monitor
• App Metadata Analyzer
• The Monitoring & Administration Topic Group
• Other Apps

Qlik Cloud

Data Capacity Reporting App

The Data Capacity Reporting App is a fully supported app distributed within the product. For more information, see Qlik Help.

Access Evaluator for Qlik Cloud

For more information, see Qlik Cloud Access Evaluator.

Answers Analyzer for Qlik Cloud

For more information, see Qlik Cloud Answers Analyzer.

App Analyzer for Qlik Cloud

For more information, see Qlik Cloud App Analyzer.

Automation Analyzer for Qlik Cloud

For more information, see Qlik Cloud Automation Analyzer.

Entitlement Analyzer for Qlik Cloud

The Entitlement Analyzer is a Qlik Sense application built for Qlik Cloud, which provides Entitlement usage overview for your Qlik Cloud tenant for user-based subscriptions.

The app provides:

• Which users are accessing which apps
• Consumption of Professional, Analyzer and Analyzer Capacity entitlements
• Whether you have the correct entitlements assigned to each of your users
• Where your Analyzer Capacity entitlements are being consumed, and forecasted usage

For more information, see The Entitlement Analyzer.

Reload Analyzer for Qlik Cloud

For more information, see Qlik Cloud Reload Analyzer.

Report Analyzer for Qlik Cloud

For more information, see Qlik Cloud Report Analyzer.

How to automate the Qlik Cloud Monitoring Apps

Do you want to automate the installation, upgrade, and management of your Qlik Cloud Monitoring apps? With the Qlik Cloud Monitoring Apps Workflow, made possible through Qlik's Application Automation, you can:

1. Install/update the apps with a fully guided, click-through installer using an out-of-the-box Qlik Application Automation template. 
2. Programmatically rotate the API key that is required for the data connection on a schedule using an out-of-the-box Qlik Application Automation template. This ensures that the data connection is always operational. 
3. Get alerted whenever a new version of a monitoring app is available using Qlik Data Alerts. 

For more information and usage instructions, see Qlik Cloud Monitoring Apps Workflow Guide.

Other Qlik Cloud Monitoring Apps

OEM Dashboard for Qlik Cloud

For more information and to download the app and usage instructions, see Qlik Cloud OEM Dashboard & Console Settings Collector.

With the exception of the Data Capacity Reporting App, all Qlik Cloud monitoring applications are provided as-is and are not supported by Qlik. Over time, the APIs and metrics used by the apps may change, so it is advised to monitor each repository for updates and to update the apps promptly when new versions are available.

If you have issues while using these apps, support is provided on a best-efforts basis by contributors to the repositories on GitHub.

Monitoring Apps for Qlik Sense Enterprise on Windows

Operations Monitor and License Monitor

The Operations Monitor loads service logs to populate charts covering performance history of hardware utilization, active users, app sessions, results of reload tasks, and errors and warnings. It also tracks changes made in the QMC that affect the Operations Monitor.

The License Monitor loads service logs to populate charts and tables covering token allocation, usage of login and user passes, and errors and warnings.

For a more detailed description of the sheets and visualizations in both apps, visit the story About the License Monitor or About the Operations Monitor that is available from the app overview page, under Stories.

Basic information can be found here:

The License Monitor 
The Operations Monitor 

Both apps come pre-installed with Qlik Sense. 

If a direct download is required: Sense License Monitor | Sense Operations Monitor. Note that Support can only be provided for Apps pre-installed with your latest version of Qlik Sense Enterprise on Windows. 

App Metadata Analyzer

The App Metadata Analyzer app provides a dashboard to analyze Qlik Sense application metadata across your Qlik Sense Enterprise deployment. It gives you a holistic view of all your Qlik Sense apps, including granular level detail of an app's data model and its resource utilization.

Basic information can be found here: 

App Metadata Analyzer (help.qlik.com)

For more details and best practices, see: 

App Metadata Analyzer (Admin Playbook)

The app comes pre-installed with Qlik Sense.

The Monitoring & Administration Topic Group

Looking to discuss the Monitoring Applications? Here we share key versions of the Sense Monitor Apps and the latest QV Governance Dashboard as well as discuss best practices, post video tutorials, and ask questions.

Monitoring & Administration 

Other Apps

LogAnalysis App: The Qlik Sense app for troubleshooting Qlik Sense Enterprise on Windows logs 
Sessions Monitor, Reloads-Monitor, Log-Monitor 
Connectors Log Analyzer 

All Other Apps are provided as-is and no ongoing support will be provided by Qlik Support.

In an effort to further clarify the differences between the Qlik Sense editions available and how Multi-Cloud ties in with those, see Qlik Sense at a glance.

A brief summary is provided in this article.

Qlik Sense is available on SaaS (Qlik Cloud) and Windows. 

Qlik Cloud allows for two different subscription types: Enterprise and Business. Qlik Sense Enterprise is the full version of Qlik Sense, supporting a full spectrum of analytics use cases on a multi-cloud platform. Qlik Sense Business is a SaaS solution that brings the power of Qlik’s third-generation analytics platform to groups, teams, and businesses that want to quickly operationalize analytics and make data-driven decisions.

Qlik Sense Enterprise on Windows is deployed on-premise and client managed. You can distribute Qlik Sense apps to cloud environments, using Qlik Sense Enterprise multi-cloud capabilities and share user management between a Qlik Cloud instance and a client-managed instance. This is only possible with a Qlik Sense Enterprise subscription.

Related Content:

Get started with Qlik Sense Enterprise SaaS 
Introducing Qlik Sense Enterprise on Windows 
Introducing Qlik Sense Business 

If you are using the SAP Application Endpoint for CDC processing and want to implement the new Full Record Mode feature with the Trigger-based endpoint, you will also need to convert the existing SAP Application Endpoint to use the SAP Application DB Endpoint.

In Qlik Replicate 2025.5 (and later versions):

Qlik Replicate 2025.5 exposes the setting directly in the endpoint Advanced tab.

1. Go to the SAP Hana Source Endpoint
2. Switch to the Advanced tab
3. Set Record Mode to Full Record

The Endpoint now has the SAP HANA source endpoint defined as the Backend DB with Version 4 Trigger in Full Record Mode enabled.

In Qlik Replicate 2024.11 SP04 to the latest 2024.11 SP:

1. Set the Backend database to the SAP Hana Trigger Based Endpoint
   
   
   
   
2. Switch to the Advanced tab and set:
   
   
   • CDC Mode: Trigger-based CDC
   • Trigger mode: Primary key only
   • Trigger-based mode: Log Table
   • Check Create CDC artifacts
     
     
     
     
3. Now set sapHanaFullRecord in More Options
   
   
   1. Go to More Options in the Endpoint settings
      
      
      
      
   2. Add sapHanaFullRecord and set it to On
      
      
      
      
4. Save the Endpoint

The SAP Hana Endpoint has Full Record Mode (version 4) enabled, which requires a Full Reload of the Source to move to this new mode.

Environment

• Qlik Replicate

After upgrading Qlik Sense Enterprise on to Windows May 2022 patch 11 or August 2022 patch 6, reload tasks may be listed as failed even if the script log completes successfully.

The engine logs (Engine\System Service_Engine_TIMESTAMP.log):

WARN QLIKSERVER XXXXX-b9df-48dc-a868-XXXX 20230130T151057.522+0100 12.1386.6.0 Command=Doc::DoSave;Result=409;ResultText=Warning: Conflict 0 0 1111411 QLK QLIKUSER XXXXX-47c2-4ea4-94c2-XXXXXX XXXXX-95f5-46e2-8b92-XXXXX ApplicationQLIK Engine Not available Doc::DoSave Doc::DoSave 409 Object write failed. XXXXXX-b9df-48dc-a868-XXXXX

The repository logs (Repository\Trace log called System_Engine_TIMESTAMP.log):

2072 20230129T193052.695+0100 ERROR QLIKSERVER System.Repository.Repository.Core.Repository.Common.TransactionUtility 185 XXXXX-d7f0-4983-8905-XXXX QLK\QLIKSERVICEUSER Error when committing The custom property value already assigned at 

Environment

Qlik Sense Enterprise on Windows May 2022, August 2022

Resolution

Warning: Modifying the Qlik Sense Repository manually is generally not supported by Qlik. Any modifications need to be done with extreme caution. Always back up your Qlik Sense database before committing changes.

This is caused by custom properties being duplicated and injected multiple times. The fix requires these duplicates to be removed.

1. Back up your Qlik Sense site. See Backup and restore Qlik Sense Enterprise on Windows.
2. Connect to the QSR Postgres database. See How to connect to the Qlik Sense Enterprise on Windows or Qlik NPrinting PostgreSQL database .
3. Identify the list of duplicate custom properties. Use the following query:
   

   SELECT "ID", "Definition_ID", "Value", "App_ID" FROM
   ( SELECT "ID", "Definition_ID", "Value", "App_ID",
   ROW_NUMBER() OVER ( PARTITION BY "Value", "Definition_ID", "App_ID"
   ORDER BY "App_ID" DESC, "ID"
   ) rn
   FROM "CustomPropertyValues"
   ) t1 WHERE rn > 1 AND "App_ID" IS NOT null;

   
   
4. If you found any duplicates in the query above, use the below cleanup script:
   

   DELETE FROM "CustomPropertyValues"
   WHERE "ID" IN
   ( SELECT "ID" FROM
      ( SELECT "ID", "Definition_ID", "Value", "App_ID",
               ROW_NUMBER() OVER ( PARTITION BY "Value", "Definition_ID", "App_ID"
                                   ORDER BY "App_ID" DESC, "ID"
                                 ) rn
        FROM "CustomPropertyValues"
      ) t1 WHERE rn > 1 AND "App_ID" IS NOT null);​

   
   
   

Cause 

This is caused by a fix QB-9058, which has been introduced in May 2022 Patch 11 and August patch 6:

Qlik Sense: Possible to apply same custom property value more than once to a single app:

Fixed an issue where it was possible via QMC or API request to apply the same custom property value belonging to the same custom property definition more than once to the same Qlik Sense app/qvf.

So from those patch it is no longer possible to have any application with a duplicate custom property.

Duplicate properties will be shown as errors in the Qlik Sense log:

The custom property value already assigned

The diagnosis script above will also expose duplicate custom properties

Internal Investigation ID(s) 

• QB-21006
• QB-17917
• QB-9058

Google Ads integration encounters the extraction error:

tap - CRITICAL (<_InactiveRpcError of RPC that terminated with:
tap - CRITICAL status = StatusCode.PERMISSION_DENIED
tap - CRITICAL details = "The caller does not have permission"
tap - CRITICAL debug_error_string = "UNKNOWN:Error received from peer ipv4:172.253.115.95:443 {grpc_message:"The caller does not have permission", grpc_status:7}"
tap - CRITICAL >
tap - CRITICAL errors {
tap - CRITICAL error_code {
tap - CRITICAL authorization_error: USER_PERMISSION_DENIED
tap - CRITICAL }
tap - CRITICAL message: "User doesn't have permission to access customer. Note: If you're accessing a client customer, the manager's customer id must be set in the 'login-customer-id' header. See https://developers.google.com/google-ads/api/docs/concepts/call-structure#cid"
tap - CRITICAL }
tap - CRITICAL request_id: "xxxxxxxxxxxxxx"

Resolution

On the Google side:

1. Sign in to the Google Ads UI and ensure that:

   • You have access to the customer account ID you’re trying to query.

   • If it’s a client account, it must be linked to a manager (MCC) account that has API access.

2. If you see that the customer account is cancelled or inactive, reactivate it by following Google’s guide:
   Reactivate a cancelled Google Ads account | support.google.com

3. If the issue persists, reach out to Google Ads API support with:

   • The error snippet

   • The request_id from your extraction logs (used by Google to trace the failed call)

On the Stitch UI side:

1. Re-authorize the Google Ads integration:

   1. Open Stitch in an incognito browser window.

   2. Go to the Google Ads integration settings.

   3. Click Re-authorize and follow the OAuth flow.

2. After re-authorizing, navigate to the Extractions tab and click Run Extraction Now.

3. If you manage multiple Google Ads accounts, note that:

   • Some accounts may work while others fail if they’re not connected to a manager account.

   • Only Ads accounts linked to a manager (MCC) have Ads API access.

   • Regular advertiser accounts must be linked to a manager account for Stitch to extract data successfully.

Prevention Tips

• Periodically verify that the connected Google Ads account is linked to a manager account and the OAuth token has not expired.

• Check for account status (ENABLED, CANCELLED, etc.) using the CustomerStatus enum | developers.google.com  if you suspect deactivation.

• Document the manager–client hierarchy for clarity when managing multiple accounts.

Cause 

The error message indicates that the Google Ads API denied permission for the request. This is a raw authorization error returned by Google Ads, specifically:

USER_PERMISSION_DENIED

The user or OAuth credentials being used don’t have permission to access the target Ads customer account.
If you’re accessing a client (managed) account, the manager account ID must be provided in the login-customer-id header.

See Google’s reference documentation in Authorizationerror | developers.google.com.

Environment

• Stitch 

Qlik Data Gateway connection details can no longer be viewed or modified. New connections cannot be created.

Existing Qlik Data Gateway connectors continue to work as expected. 

The following error is displayed in the connection details:

Obsolete connection type

Resolution

A temporary fix has been deployed in the Qlik Cloud back end while a permanent fix is being developed, which will be deployed soon.

For the time being, the issue will resolve itself after a period of time, or by restarting your Data Gateway Direct Access server.

Internal Investigation ID(s)

DCAAS-2117

Environment

• Qlik Data Gateway Direct Access

When attempting to add an Automation to an Execute Automation button, the Automation is not listed in the drop-down menu.

Cause

For the Execute Automation button, a maximum of 100 automations can be displayed for selection under Automation. 

Resolution

If you have access to more than 100 automations and cannot find the automation you want, you can use the automation ID.  The automation ID is in the segment after /editor/ in the URL before /edit or /history.

For example, in qlik.com/automations/editor/6c201b49-cz2e-00dc-8040-464ca41457b0/edit?resourceName=Active%20Intelligence, the automation ID is 6c201b49-cz2e-00dc-8040-464ca41457b0.

For more information about identifying automation IDs, see How to identify the automation Id and job Id in Qlik Application Automation.

Related Content

Qlik Help entry: Creating Buttons

Environment

Qlik Cloud 

This error occurs with the Google Cloud SQL PostgreSQL database integration and it displays as below in the extraction logs:

Fatal Error Occured - ERROR: temporary file size exceeds temp_file_limit 

Resolution

To resolve this issue, you need to increase the temp_file_limit parameter in your PostgreSQL configuration

Here are the steps to fix it:

1. Access your Google Cloud SQL instance settings.

2. Locate the database flags or parameters section.

3. Find the temp_file_limit flag and increase its value.

   • The value is specified in kilobytes (kB).

   • The default in PostgreSQL is -1, which means no limit. However, Cloud SQL may enforce a smaller custom value depending on your instance configuration.

4. If you’re unsure about the appropriate value, start by doubling the current limit and adjust as needed based on your workload. Increasing this limit allows larger queries to complete but may also increase storage usage, so monitor performance and disk space after making the change.

5. Save the changes.
   Updating database flags in Cloud SQL typically requires a restart of the instance for the new settings to take effect.

After modifying the temp_file_limit, restart your PostgreSQL instance (if required) and run an extraction in Stitch.

Cause 

The error message indicates that the temporary file size has exceeded the temp_file_limit in your Google Cloud SQL PostgreSQL database. This limit is set to control the maximum size of temporary files used during query execution.

Related Content

See Google’s documentation on configuring database flags here:
Configure database flags | cloud.google.com

Environment

Stitch 

Question

 I would like to get a full list of integrations and configuration details of those integrations. Things like the list of tables we are syncing, the schedule it is being synced on, etc.

Can you provide a way to let Stitch users export the details of the integrations in one file? It should show the list of tables replicated, replication frequency, the integration settings to show how its configured.

You can accomplish this with the Qlik Talend Cloud Migration Toolkit: stitch-assets-inventory | Qlik Help

Alternatively, if you have an Advanced or Premium subscription you can leverage Stitch's Connect API to obtain metadata on your account:

Stitch Connect API Reference# API functionality (Qlik Stitch Documentation)

For any details not available in the above, please submit a feature request via qlik-product-insight

Environment

Stitch 

Automations using Qlik Reporting Service blocks fail with the following:

status:403 

forbidden request

Details in the error status messages indicate:

user does not have permissions to export the report

Resolution

If the automation has previously run successfully and no action has been taken by the Tenant Administrator to use the Qlik Reporting Service content roles:

• Grant the appropriate space role to the automation owner (the persona executing the automation). See Permissions | help.qlik.com for details. This can be done by the Space Owner. 

If the Tenant Administrator has started to apply custom role control:

• The automation owner must work with the Tenant Administrator to obtain the appropriate access. See Permissions | help.qlik.com for details.

Cause

The introduction of custom roles supporting the Qlik Reporting Service requires the automation owner executing an automation calling the following Qlik Reporting Service Blocks to have the appropriate platform and space roles that govern report execution from a specific app.

See Permissions | help.qlik.com for details. 

The blocks: 

• Generate Report
• Get PixelPerfect Report
• Get Tabular Report  

The Qlik Reporting Service is a value-add service in which customers have long requested the ability to control who can use the services and produce (metered) reports.   

The release of custom roles to support Qlik Reporting Service brings consistency to all use cases, ensuring that users executing the report have the appropriate tenant role and space permission to the application to know what report data is being produced.  

• The Default user continues to be given full access to execute Qlik Reporting Service activity (subject to space roles) 
• Space roles are enforced, which can result in a breaking change for an automation owner if they did not previously have access to the Space in which the source app exists. In the case of the above-mentioned Qlik Automation reporting blocks, this results in a stricter user role configuration.   

Environment

• Qlik Cloud
• Qlik Automation
• Qlik Reporting Service

Does a Qlik Sense pivot table have a hard limit on its dimensions and measures?

Answer

Qlik Sense pivot tables have a limit of 1000 measures and 1000 dimensions. 

Approaching this limit is not recommended. Managing measures and dimensions of this volume will become difficult and impractical.

Environment

• Qlik Cloud Analytics
• Qlik Sense Enterprise on Windows

When you need to integrate auth0 JWT Bear Token auth with Talend tRestRequest component, it is possible to use JWT Bearer Token with Keystore Type : Java Keystore *.jks to achive this.

How To

Please follow the some similar steps from Obtaining a JWT from Microsoft Entra ID | Qlik Help

1. Open https://dev-xxxx.us.auth0.com/.well-known/jwks.json in a Web browser.
   Reference: json-web-key-sets| auth0.com 
2. Copy the String value from the x5c field of the matched key and save it to a text file.
   Convert the text file to an talend-esb.cer file, for example:

   -----BEGIN CERTIFICATE-----
   MGLqj98VNLoXaFfpJCBpgB4JaKs
   -----END CERTIFICATE-----

3. Import this trusted key into your keystore JKS using Java keytool.

   keytool -import -keystore talend-esb.jks -storepass changeit -alias talend-esb talend-esb.cer -noprompt

4. Use this talend-esb.jks in tRestRequest with the following configurations

   Security: JWT Bearer Token
   Keystore File: /path_to/talend-esb.jks
   Keystore Password : changeit
   Keystore Alias : talend-esb
   Audience: "https://dev-xxxx.us.auth0.com/api/v2/"

5. Use the bear token fetched from  https://dev-xxxx.us.auth0.com/oauth/token to send request to tRestRequest defined endpoint for testing.

Environment

• Talend Studio 
• Talend ESB 

Integration fails with the following error:

tap - CRITICAL 'search_prefix'
tap - Traceback (most recent call last):
tap - File "/code/tap-env/bin/tap-s3-csv", line 10, in <module>
tap - sys.exit(main())
tap - ^^^^^^
tap - File "/code/tap-env/lib/python3.12/site-packages/singer/utils.py", line 235, in wrapped
tap - return fnc(*args, **kwargs)
tap - ^^^^^^^^^^^^^^^^^^^^
tap - File "/code/tap-env/lib/python3.12/site-packages/tap_s3_csv/__init__.py", line 81, in main
tap - config['tables'] = validate_table_config(config)
tap - ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
tap - File "/code/tap-env/lib/python3.12/site-packages/tap_s3_csv/__init__.py", line 63, in validate_table_config
tap - table_config.pop('search_prefix')
tap - KeyError: 'search_prefix'
main - INFO Tap exited abnormally with status 1
main - INFO No tunnel subprocess to tear down
main - INFO Exit status is: Discovery failed with code 1 and error message: "'search_prefix'". 

Resolution

Improving the integration to gracefully handle the missing key when an update to the connection/config occurs is currently on the roadmap. The R&D team is working on this behavior and a minor version upgrade is expected down the line; however, there is currently no ETA.

If you encounter this error with your AWS S3 CSV integration, please reach out to Qlik Support for further assistance.

Cause

The issue occurs due to missing keys in the configuration. Specifically, an update to the connection settings removed or modified the search_prefix, resulting in the key being absent from the config expected by the integration.

Environment

• Stitch 

The following IBM mainframe error occurs with the ARC CDC Solutions endpoint when the wrong ARC installation files are used:

Daemon (ATTDAEMN): 09.30.44 STC06957 ASTB1001E CDC library provided in STEPLIB but ATYLIB DD card missing - no CDC 09.30.44 STC06957 ASTB1012E ERROR=ABEND in effect 

Sp15-620271-ARC-mvs.zip is confirmed to be the full patch while ARC_620271_mvs.zip is a partial patch.

Resolution

Use ARC installation files that have SP prefixes in the file name.

Cause

ARC installation files without the SP prefixes are partial installation files that may not contain all the components that you need.

Environment

• Qlik Replicate

The measure value is suddenly not displayed correctly, but it started to show null value instead. It used to show a proper data until Nov 2024 release or earlier.

The issue is observed when:

• Measures have no aggregation function (such as SUM(), COUNT())
• Fields include only one data and null value

Environment

• Qlik Cloud (at documentation)
• Qlik Sense Enterprise on Windows May 2025 and November 2025

Resolution

QCB-33031 will be fixed in Qlik Cloud at the first opportunity. Qlik Sense Enterprise on Windows will have the fix introduced in the next major release in 2026.

Workaround One

Apply aggregation or Only() function to the affected measure.

Workaround Two

For Qlik Sense Enterprise on Windows, add the parameter UseTableEvaluatorWhenApplicable=0 to the Qlik Sense engine settings.ini file. The change must be done on all engines, if more than one is in use.

The setting indicates engine to use the old way to calculate the measures without aggregation. It is slower, but the behavior remains what it was back in Qlik Sense November 2024 and earlier.

See How to modify Qlik Sense Engine's Settings.ini for reference. 

Cause

The difference in behavior is due to an internal change in the Qlik Sense Engine introduced to improve performance.

Previously, when a measure was defined directly as a field without an aggregation, the Engine automatically applied the Only() function. This function returns a value if the field contains only a single distinct (non-null) value. 

See The importance of Only().

However, appending Only() function leads to slow performance. To optimize performance, the Engine now uses a more efficient calculation method. As a side effect, when a field contains one valid value and one null value, the result is returned as null instead of the expected value.

This issue has been identified as QCB-33031, and will be fixed to display the proper value instead of null in this scenario.

Internal Investigation ID(s)

QCB-33031

You may encounter this issue in which your Stitch integrations remain paused after your account has been renewed, reactivated after a 40-day inactivity pause | Qlik Stitch Documentation, or your account displays the error "You are over your current plan destination limit of 1. To continue loading data, remove any excess destinations or upgrade." 

Even though your account has been modified, the Stitch account itself has not fully updated and is preventing account activity.

Resolution

To resolve, please reach out to the Qlik Support team. They will be able to review your account if unpausing it will be possible or if you will need to discuss the status of your contract with your account management team.

Cause

The Stitch account is not capturing the changes to your billing and contract details.

Environment

• Stitch 

Google Ads extractions fail with:

tap - CRITICAL 504 Deadline Exceeded
tap - grpc._channel._InactiveRpcError: <_InactiveRpcError of RPC that terminated with:
tap - status = StatusCode.DEADLINE_EXCEEDED
tap - details = "Deadline Exceeded"
tap - debug_error_string = "UNKNOWN:Error received from peer {grpc_status:4, grpc_message:"Deadline Exceeded"}"
tap - >

main - INFO Exit status is: Discovery succeeded. Tap failed with code 1 and error message: "504 Deadline Exceeded". Target succeeded.

Resolution

This error is often transient and will not require any action to alleviate. If the error is persistent, review your Tables to Replicate and consider de-selecting unneeded tables or columns. If the issue remains, please reach out to Qlik Support to discuss your use-case and further review the integration settings.

Cause

The error "504 Deadline Exceeded" indicates that the extraction timed out due to a lack of response from the Google Ads API. By default, Stitch allows up to 15 minutes for a response before terminating the request.

Possible reasons the Google Ads API may exceed this threshold include:

• Large or complex queries: This can happen when Stitch issues requests with a wide date range, a large number of selected fields, or the source data has deeply nested data structures.
• Google Ads API Limits and Quotas| developers.google.com
• Network latency or backend delays: Delays between Stitch and Google Ads, or internal processing delays within Google Ads, can also contribute to timeouts.

Environment

Stitch 

Stitch Support frequently receives questions regarding the invocation of the PUBLIC role with Snowflake. When setting up a database user following Create a Stitch database and database user (Qlik Stitch Documentation), users will notice that the Stitch user executes GRANT statements on the PUBLIC role. This behavior can raise questions about role-based access and security implications within Snowflake.

Resolution

Manually adjust permissions in Snowflake as needed. If you prefer Stitch offers a more streamlined approach in its behavior, please submit a feature request. Refer to New Process for Submitting a Feature Request for All Talend Customers and Partners  on how to submit a feature request.

Cause

By default, Stitch grants the PUBLIC role access to schemas and objects it creates in Snowflake. This behavior often raises questions from users who are concerned about broad access permissions.

The reason Stitch does this is because it cannot assume which specific roles or users in your organization should have access to the data. Granting access to the PUBLIC role ensures that Stitch can write data successfully without making assumptions about your internal role structure.

This default behavior is not a requirement from Snowflake itself, but rather a design decision by Stitch to simplify initial setup and avoid permission-related sync failures.

If this approach does not align with your organization’s security policies, you may manually revoke access from the PUBLIC role after the initial sync. However, this step must be repeated each time a new integration runs or a new schema is created, which may not be scalable.

Snowflake supports granular permission control via the REVOKE command, allowing you to adjust access as needed:

🔗 REVOKE <privileges> … FROM ROLE | docs.snowflake.com

While this manual revocation process works, it requires ongoing attention. If tighter access control is a priority and manual intervention isn’t feasible, you may want to consider alternative destinations or workflows.

Environment

• Stitch 

MySQL source tables with invisible columns crash a Qlik Replicate task on start. The following error is logged:

[INFRASTRUCTURE ]E: Process crashed with signal 11, backtrace: !{/opt/attunity/replicate/lib/at_base.so!4db3bd,/opt/attunity/replicate/lib/at_base.so!3a3938,/opt/attunity/replicate/lib/at_base.so!505053,/usr/lib64/libc.so.6!4e5b0,/opt/attunity/replicate/lib/libarepmysql.so!2b931,/opt/attunity/replicate/lib/libarepmysql.so!2e094,/opt/attunity/replicate/lib/libarepmysql.so!2e3c9,/opt/attunity/replicate/lib/libarepbase.so!4cecbb,/opt/attunity/replicate/lib/libarepbase.so!4d814e,/opt/attunity/replicate/lib/libarepbase.so!4681e2,/opt/attunity/replicate/lib/libarepbase.so!55fd36,/opt/attunity/replicate/lib/libarepbase.so!560108,/opt/attunity/replicate/lib/libarepbase.so!56b0ee,/opt/attunity/replicate/lib/libarepbase.so!5a1bca,/opt/attunity/replicate/lib/libarepbase.so!77d496,/usr/lib64/libpthread.so.0!81ca,/usr/lib64/libc.so.6!398d3,}! [1000100] (at_system_posix.c:575)

Resolution

This issue is caused by defect RECOB-10177. Future patches for Qlik Replicate will incorporate the handling of invisible columns for MySQL tables. 

Fix Version

2025.5 SP03 and newer versions.

Cause

Qlik Replicate could not handle invisible columns for the MySQL source.

Internal Investigation ID(s)

2025.5 SP03

Environment

• Qli Replicate

Qlik Sense Repository service will log performance counters, and set them up on startup. Unfortunately sometimes the base counters are corrupt so the start can't proceed.

The error in the logs:

fatal exception during startup Cannot load Counter Name data because an invalid index '' was read from the registry. at System.Diagnostics.PerformanceCounterLib.GetStringTable(Boolean isHelp)?? ? at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)?? [...] at System.Threading.ThreadHelper.ThreadStart() 3facc7ff-8275-4847-b3b7-338d32c4d1c5 its the repo checking the counter which doesn't exist

Qlik Sense April 2019 will log information including instructions to resolve the issue. See the related Release Notes for ID QLIK-92800:

"Failed to initialize usage of Windows Performance Counters. Make sure that performance counters are enabled or try rebuilding them with "lodctr /R" 

Resolution

Option 1

A workaround is provided in repairing the Windows Performance Counters:

1. Open an elevated command prompt (run as administrator)
2. Rebuild the counters with the following commands: 
      
   cd c:\windows\system32
   lodctr /R
   cd c:\windows\sysWOW64
   lodctr /R
   
   If you get the response Error: Unable to rebuild performance counter setting from system backup store, error code is 2, run the same command once more.
   
   A successful run will say:
   
   Info: Successfully rebuilt performance counter setting from system backup store

Pitfalls:

If you get as a return:

Error: Unable to rebuild performance counter setting from system backup store, error code is 5

then your prompt was not elevated. Elevate the command prompt with administrator permissions.

If the commands are successful yet symptoms persist, perform Option 2.
 

Option 2 

Ensure that the counters are not disabled in the registry

The counters may be disabled via registry settings. Please check the following registry locations to ensure that the counters have not been disabled.

HKLM\System\CurrentControlSet\Services\%servicename%\Performance

%servicename% represents any service with a performance counter. For example: PerfDisk, PerfOS, etc.

There may be registry keys for "DisablePerformanceCounters" in any of these locations. As per the following TechNet article, this value should be set to 0. If the value is anything other than 0 the counter may be disabled.

Disable Performance Counters

http://technet.microsoft.com/en-us/library/cc784382.aspx

• A value of 1 means the counter is disabled.
• A value of 2 means the 32-bit counter is disabled.
• A value of 4 means the 64-bit counter is disabled.
• Please make sure that none of the Perfxxxxx are have a key within them called "DisablePerformanceCounters". If they do, please make sure that the value is set to 0.

ref. https://support.microsoft.com/en-us/help/2554336/how-to-manually-rebuild-performance-counters-for-windows-server-2008-6

Once done, return to Option 1 

Environment:

Qlik Sense Enterprise on Windows