There are JVM hanging errors in wrapper.log during job running for Talend Remote Engine Server

JVM appears hung: Timed out waiting for signal from JVM.
JVM did not exit on request, terminated
JVM exited in response to signal SIGKILL (9).
Unable to start a JVM
<-- Wrapper Stopped   

When the CPU is high (time interval) the jvm exited and also you see JVM hanging errors in wrapper log.

This is because when the jvm is not getting response, the wrapper tries to restart the container and try to recover from the hung behavior. 

Resolution

1. Please check that the memory you have allocated to your remote engine is enough to handle the jobs that you run.
   In order to allocate memory to your remote engine, please check here: Specifying Java heap size for a Remote Engine service.
   To monitor the resource consumption, and check if you are consuming too much memory, please use the following tools for monitoring.
   • Monitoring the resource consumption on Remote Engine
   • Showing JVM resource usage during Job or Route execution
2. Even when you check the resource consumption, the data may show normal activity. For further investigation, please try the followings:
   • Check Event Logs: Review the event logs for system messages or events occurring around the time of termination for more context. (For example, for Linux, use commands like journalctl, and for Windows, Windows Event Viewer).
   • Monitor System Activity: Use tools to monitor resource usage (For example, for Linux, top, htop, or performance monitor tools like atop, and for Windows, Task Manager or Performance Monitor) to track CPU, memory, and disk usage.
   • Investigate External Scripts or Tools: Ensure no external scripts or tools are configured to terminate the JVM under certain conditions.

Cause

1. JVM/CPU/Disk usage is very high
2. Some scripts or automated system management tasks might be configured to terminate processes under specific conditions
3. The OS may terminate a process if the system runs out of resources, such as memory

Environment

Talend Cloud 

Qlik Replicate was upgraded to 2022.11. The Qlik Replicate UI service fails to start post-upgrade. 

Environment

Replicate version 2022.11 

Resolution

Review the repuictl.log stored in ~\replicate\data\logs and look for the following message:

Repository 'Global' or one of its ingredients are out of date, please run the following command to upgrade the repository: RepUiCtl.exe repository upgrade --repository <repository_full_path>

After verifying the error:

1. Open a command prompt as Administrator
2. Change directory to ~\replicate\data\bin
3. From bin run: 
   
   RepUiCtl.exe repository upgrade --repository "d:\Program Files\Attunity\Replicate\data\GlobalRepo.sqlite"
   
   In our example, our install folder is on D:\. Modify this accordingly. 
   
   
4. You will receive a confirmation:
   
   Repository "GlobalRepo.sqlite" has been successfully upgraded.
   Replicate Control Program completed successfully.
   
   
5. Start the Qlik Replicate UI Server Service.

Cause

the "GlobalRepo.sqlite" file did not get update during the upgrade process.

In Qlik Sense, when there is a commented out portion of the script, if "//" is deleted and the script is saved, all the text will turn black and all syntax highlighting will be lost. If pages of the script are toggled between, a message that says "we have disabled syntax highlight to maintain performance" appears and the highlighting will come back but if previous steps are followed again,commenting will also be disabled again.  

This is working as designed.

It is the current solution for dealing with deeply nested if statements. In many cases these deeply nested if blocks will cause real performance issues (crashing the browser). The best practice is to not use nested ifs when possible. The commenting/uncommenting works because we count the levels. Pretty sure 10 levels deep we trigger the perf warning. So if they comment out one and it's only 9 it won't complain.

Environment: 

Internal Investigation ID(s):

Talend Remote Engine Heart Beat is failing hourly with 'GOAWAY received' error and the karaf.log shows below:

2024-08-01T10:16:58,638 | ERROR | pool-28-thread-1 | JAXRSUtils | 469 - org.apache.cxf.cxf-rt-frontend-jaxrs - 3.6.2 | | Problem with writing the data, class org.talend.ipaas.rt.engine.model.HeartbeatInfo, ContentType: application/json
2024-08-01T10:16:58,638 | WARN | pool-28-thread-1 | PhaseInterceptorChain | 467 - org.apache.cxf.cxf-core - 3.6.2 | | Interceptor for {http://pairing.rt.ipaas.talend.org/}PairingService has thrown exception, unwinding now
org.apache.cxf.interceptor.Fault: Problem with writing the data, class org.talend.ipaas.rt.engine.model.HeartbeatInfo, ContentType: application/json
Caused by: java.io.IOException: /<IP>:<port>: GOAWAY received

This could also be a possible solution when the following error is also showing in the log:

Caused by: java.io.IOException: HTTP/1.1 header parser received no bytes

Resolution

1. Stop Remote Engine.
2. Edit the <RemoteEngineInstallation>/etc/org.talend.ipaas.rt.pairing.agent.cfg file and replace the line 

   heartbeat.interval=60 (by default) 

   with 

   heartbeat.interval=65

3. In the file <RemoteEngineInstallation>/etc/system.properties, remove or comment out the line below (if it exists):
   

   org.apache.cxf.transport.http.forceVersion=1.1​

4. Restart Remote Engine.

Do not set heart interval to more than 180 seconds(3 mins). If Talend Cloud does not receive a heartbeat from the Remote Engine for more than 3 mins, it will show the Remote Engine's status as unavailable.

Cause

The connection to the server pair.xx.cloud.talend.com is kept during 60 seconds and Heartbeat.interval > 60 seconds allows to close this connection and prevent "GOAWAY received" error message.

Related Content

For more information about heartbeat concept and heartbeat interval, please refer to documentation:

Monitoring-remote-engine-health

Internal Investigation ID(s)

 Internal Jira Case ID: TMC-4122

Environment

Talend Cloud 

Qlik Answers is Qlik's personalized AI assistant that generates on-point answers from your own trusted business content. See this article to learn how to get started with Qlik Answers

This connector unlocks new powerful use cases like indexing new data ad-hoc and taking your action oriented automations to the next level by including unstructured insights. This article explains how the Qlik Answers connector in Qlik Application Automation can be used.

Article contents

• Authentication
• Use cases
• 1. Re-indexing a knowledge base
• 2. Ask questions
• Notes
• Related Content

Authentication

This connector does not require additional configuration to authenticate, it will automatically connect to the automation owner's Qlik account. Whenever blocks of this connector are executed, they will use that account.

Use cases

For this connector's first release, we will introduce blocks that can re-index knowledge bases and ask questions to an assistant. We will deliver more blocks in future releases, do not hesitate to request new blocks through Ideation.

1. Re-indexing a knowledge base

This use case focuses on ad-hoc updates to the knowledge base. The creation and initial configuration of a knowledge base should happen through the Qlik Answers UI as described here:

Once your knowledge base is configured and you've set up a data connection to a cloud storage location, you can then use Qlik Application Automation to add specific files to the Cloud Storage location and trigger a re-indexing. This could be useful in scenarios when you only want to index specific records that might depend on a context.

For this use case, you can use the blocks Add Data Source To A Knowledge Base and Sync Knowledge Base Data Source. The below example will fetch incidents from ServiceNow, store them in a Dropbox folder and then add the Dropbox folder as a data source to a Knowledge Base in Qlik Answers. After this, the data source will be synced to the knowledge base index.

2. Ask questions

By using the blocks Create Thread and Execute Synchronous Prompt, you can ask questions from an assistant to enrich other messages that are sent through automations with unstructured insights. In the below example, these blocks are added to the existing "Notify your team on Microsoft Teams based on a measure" template that can be found in the template picker:

Notes

Don't ask a question immediately after indexing. Asking a question should be done after the knowledge base has completed indexing successfully.

Related Content

• Introducing Qlik Answers
• Qlik.com product page for Qlik Answers

Environment

• Qlik Cloud Analytics
• Qlik Application Automation
• Qlik Answers

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.

This article outlines how Qlik NPrinting and Qlik Sense Enterprise on Windows consume resources. 

Environment

• Qlik NPrinting
• Qlik Sense Enterprise on Windows

Resolution

Qlik NPrinting interacts with Qlik Sense when a metadata reload or a task execution is started (a report preview or an On-Demand request is essentially the same as a task execution).

For metadata reloads, Qlik NPrinting directly opens a connection with the Qlik Sense Server, and the following actions are performed on the Qlik Sense side:

1. The Qlik Sense app is opened in the background
2. Section access is removed (Qlik NPrinting opens the app as an admin)
3. All selections, bookmarks, and reductions are removed
4. Qlik Sense sends the metadata to Qlik NPrinting
   This includes: all object names and types, all fields and their values, and all variables
5. NPrinting collects this information and organizes it in the database

The resource consumption is mainly on the Qlik Sense side. In particular, opening the app requires RAM, and removing selections/bookmarks/Session Access requires calculations that consume CPU.

When a task is run, Qlik NPrinting connects to the Qlik Sense Server, which performs the following:

1. Open the Sense app(s)
2. Remove the selections
3. Apply the filters to generate the reports
   Note: Cycles, Pages, and Levels are essentially filters on each field value
4. Export each single table or image requested by each template with the correct selection

This is quite expensive in terms of resources, especially if many filters are present (or Cycles/Levels/Pages) because a filter is essentially a selection on the app and each selection requires calculations and, therefore, CPU usage.

Moreover, Qlik NPrinting is multi-treading. This means that multiple instances of the same app can be opened in Qlik Sense at the same time. This enables Qlik NPrinting to execute the requests of filter applications and table exports in parallel. On the other side, having many applications opened at the same time represents a resource cost for Qlik Sense.

The maximum number of apps that can be opened at the same time equals the number of logical cores on the Qlik NPrinting Engine machine. You have to sum them up if more engines are installed.

The situation is more complex if Session Access is used. In this case, Qlik NPrinting cannot apply all the requests on the apps in the same session. The app must be closed and re-opened for each Qlik NPrinting user, with a high consumption of RAM and CPU on the Sense side. This also loses the possibility to apply many of the Qlik NPrinting optimizations for the report generation.

On the Qlik NPrinting side, some resources are used by the Engine service to keep in memory images, tables, and other values sent by Sense. NPrinting then needs to place these objects correctly on the template. Also, this action is performed by the Qlik NPrinting Engine service and it is more resource-consuming on the Qlik NPrinting side. Generally, we do not expect a problematic consumption in a supported NPrinting environment, unless very heavy and complex reports are generated or many tasks are run at the same time. The main resource request is on the Qlik Sense side.

Frequently Asked Questions

Does Qlik NPrinting respect the Qlik Sense load balancing rules?

Qlik NPrinting uses the same proxy to connect as an end user. Load balancing rules will be respected.

The failure of Talend CICD pipeline building is caused by missing Big Data Dynamic Distribution related jar files.

Resolution

Adding the following lines dedicated to Talend Big Data Setting in maven_settting.xml file

or 

Creating a local nexus proxy repository mapping to Talend Dynamic Distribution URL and adding the local nexus repository URL to maven_setting.xml file.

Talend Proxy: https://talend-update.talend.com/nexus/content/groups/dynamicdistribution/

The credentials to be used to connect to this Talend Proxy are: 

UserName: studio-dl-client
Password: studio-dl-client

vi maven_settings.xml

…

   <servers>
        <server>
           <id>talend-bigdata</id>
           <username>studio-dl-client</username>
           <password>studio-dl-client</password>
       </server>
   </servers>

<repositories>
               <repository>
                   <id>talend-bigdata</id>
                   <name>central-talend</name>
                   <url>https://talend-update.talend.com/nexus/content/groups/dynamicdistribution/</url>
                   <layout>default</layout>
               </repository>

</repositories>

<pluginRepositories>
               <pluginRepository>
                   <id>talend-bigdata</id>
                   <name>central-maven</name>
                   <url>https://talend-update.talend.com/nexus/content/groups/dynamicdistribution/</url>
                   <layout>default</layout>
               </pluginRepository>

<pluginRepositories>

…

Cause

From log analysis, we found the related jar files are Big Data Dynamic Distribution Customized version, and It is also missing in repository in the used maven_setting.xml file.

Related Content

 Adding the latest Big Data Platform dynamically (Dynamic Distributions)

Environment

• Talend Studio
  
• Talend Big Data 

Qlik NPrinting Excel reports fail when a level is inside hidden columns. The following error is shown:

Object reference not set to an instance of an object

The error message occurs when the columns where a level is placed are hidden.

Resolution

Upgrade to NPrinting February 2024 IR (24.4.5) or later versions.

Cause 

OP-95820, resolved in Qlik NPrinting February 2024 IR (24.4.5) or later versions.

Internal Investigation ID

OP-95820

Environment

Qlik NPrinting May 2023

• Timeline
• Standard run vs third-party run
• Standard runs
• Third-party runs
• Possible third-party runs
• Transition of existing entitlements
• Starting Jan 30th (introduction of third-party runs, current packaging still applies)
• Starting April 2nd (switch to new packaging)
• FAQ

 

Timeline

The below timeline illustrates how the various stages of this packaging update will happen. In-between each stage should be sufficient time to analyze your usage and prepare for the enforcement.

• January 30th – Introduction of third-party runs
• April 2nd – New third-party packaging is available for purchase 
• May 1st – Enforcement
  • Third-party limits for seat-based licenses
  • Third-party overages for capacity licenses

Standard run vs third-party run

Standard runs

An automation run is considered a standard run if it only executes blocks from the following categories:

• All Qlik connectors (Qlik Cloud Services, Qlik Reporting, Qlik AutoML, Qlik …)
• Base blocks (excluding Call URL & Cloud Storage)
• Mail & Microsoft Outlook

Example:

 

Third-party runs

An automation run is considered a third-party run if it executes any blocks that are not in the standard connector categories.

As a rule of thumb, a standard run will execute one or more blocks from third-party connectors. Among others, third-party connectors are connectors like Slack, Amazon S3, Microsoft Excel, Call URL. A full overview of all automation connectors if available here.

Example:

Every run of this automation will execute the Send Message (Slack) block.
This will make every run a third-party run as the Slack connector is a third-party connector.
The “Contains third-party blocks” label indicates that the automation contains an active third-party block.

Possible third-party runs

For a run to be considered a third-party run, we only evaluate executed blocks. If the third-party blocks in the automation were not executed, the run will not count as a third-party run. A block not being executed could be caused by many factors like Condition blocks, Filter List blocks, deactivated third-party blocks, ...

This illustrates that an automation with a “Contains third-party blocks” label will not necessarily generate third-party runs on every run.

Example:

This automation will only execute the Send Message (Slack) block if the reload fails (from the Do Reload block). This means it will only generate third-party runs depending on the state of the Condition block.

Transition of existing entitlements

Starting Jan 30th (introduction of third-party runs, current packaging still applies)

1. Customers who are entitled to included runs will get these as third-party runs
2. Purchased runs will be converted to third-party runs
3. Renewals before the end of March will maintain the same included third-party runs until next renewal.

Starting April 2nd (switch to new packaging)

1. Every new purchase will be using the new packaging
2. Renewals will revert third-party runs to the edition included quantity of the new packaging + any purchase of third-party runs using the new packaging

FAQ

1. Will max concurrency be shared across run types?
Yes, both run types will count towards the same max concurrency.

2. Will usage of Qlik APIs through the Call URL block or other generic connectors count towards third-party runs?
Yes, when these blocks and connectors are used to make API requests to Qlik APIs, they will still count towards third-party runs. If you are missing blocks or functionality in a Qlik connector, please create an improvement request on our Ideation portal or support an existing request.

3. Will the new packaging have an included amount of third-party runs?
Yes, the new packaging will continue to provide some third-party runs for most editions of Qlik Cloud. More information on the editions and included amounts will be shared soon.

4. Why are some automations with third-party blocks missing the label "Contains third-party blocks"?
An automation will only receive the label when someone performs a manual run or saves it in the editor. We are planning a new update that will apply this label to all automations with active third-party blocks regardless of someone saving them or not.
Please note that regardless of this label being on an automation or not, automation runs will still be evaluated and receive a correct billable yes/no label.

All supported Qlik Sense releases support:

• SMB 3.0-based file shares, including standard Windows file shares
  
  
• High-end NAS under particular scenarios
  
  See Qlik Sense and NAS devices details.
  
  
• NFS-based files share

  To enable compatibility with an NFS share, add the MapNetworkDrives=1 parameter in the Qlik Sense settings.ini. 
  
  See How to modify Qlik Sense Engine Settings.ini for details on how to customize the settings.ini.

Related Content

• System requirements for Qlik Sense Enterprise on Windows
• Qlik Sense for administrators: Creating a file share
• Does Qlik Replicate support NFS Shared storage? 

You will find your tasks could not be executed when using artifact task with "use latest version" selected. On the Job Conductor page UI, it shows "Generated job not found" and there are a lot of errors in the technical log of Job Server like "Asset search returned on results"

Generatedjobnotfound

Unexpected exception on: ExecutionTask[****]
org.quartz.JobExecutionException: org.talend.administrator.scheduler.exception.ExecutionTaskException: Asset search returned no results

Resolution

Implement Retry Mechanism for Artifact Repository Connectivity in TPS-5555 patch.
The following is the details of improvement that was made may help with this random issue.
TPS-5555 (cumulative patch).

If you are using a patch version that is prior the TPS-5555 patch, please upgrade to the patch TPS-5555 or latest one.

Cause

There might be a nexus connection issue or random nexus API failure 500 which causes retrieving latest artifact action failed . It randomly occurs on a specific version of Talend Administration Center.

Internal Investigation ID(s)

Internal Jira issue: TAC-17397

Environment

Talend Administration Center 

A table with a JSON B (LOB) datatype column did not replicate this field to the target table. The task was run in CDC mode. 

Checking in the table create DDL found that there were was no primary key or unique index on the table.

Limitation:

LOB columns are not replicated in CDC mode when the table has no PK or UK.

Resolution:

Add a key to the source table or use the table in a Full Load only task.

Related Content

Replicate - Oracle source: replicating LOB columns via ROWID if the table has no Primary Key or Unique Index
An Introduction to Qlik Replicate Tasks: Full Load vs CDC
Qlik Replicate: Support JSONB datatype for PostgreSQL ODBC data source

Please note that due to changes in how browsers handle third-party cookies, you may wish to instead leverage the new qlik-embed framework with OAuth2 for your embedding needs, rather than the guidance in this tutorial.

In Qlik Cloud Services (Qlik Sense Enterprise SaaS), it is possible to get the iFrame HTML code to embed a chart in a webpage by right-clicking that chart and choosing "embed chart".

However, just placing this code on a web page is not sufficient to handle the authentication part.

The information provided in this article provides an example of how this can be achieved. Further customization is likely necessary. For assistance, join our active community in the Integrations and Extensions forum or contact our Consulting Services for an engagement. 

Environments:

• Qlik Cloud Services April 2019 and later

Resolution:

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.

Steps

1. Open the Qlik Tenant Management Console
2. Scroll to Integration Settings
3. Open Web
4. Click Create new 
5. Fill out the form:
   • Name: The name of the integration 
   • Add an origin: The allowed origins for the requests (such as the webserver hosting the integrations)
6. Click Create to confirm
7. Open Content Security Policy in the Integrations Settings section 
8. Click Add
9. Fill out the form:
   • Name: The name of the integration
   • Origin: The allowed origins for the requests (such as the webserver hosting the integrations)
   • Directive: Choose frame-ancestors
10. Click Add to confirm
11. Copy the script provided in this example:
    
    To handle the authentication and be able to see the chart on an external web page, the parent site needs to do a redirection and let the user authenticate, below is a code example of how to do that.
    

    <!DOCTYPE html>
    <html lang="en">
    
    <head>
      <meta charset="UTF-8">
      <meta name="viewport" content="width=device-width, initial-scale=1.0">
      <meta http-equiv="X-UA-Compatible" content="ie=edge">
      <title>Document</title>
      <script type="text/javascript">
        const webIntegrationId = "g-yrbnOz9wV5-YnIqYLZMgfAxf_iKg30";
        function login() {
          function isLoggedIn() {
            return fetch("https://yourtenant.eu.qlikcloud.com/api/v1/users/me", {
              method: 'GET',
              mode: 'cors',
              credentials: 'include',
              headers: {
                'Content-Type': 'application/json',
                'qlik-web-integration-id': webIntegrationId,
              },
            }).then(response => {
              return response.status === 200;
            });
          }
          return isLoggedIn().then(loggedIn => {
            if (!loggedIn) {
              // check login
                window.top.location.href = "https://yourtenant.eu.qlikcloud.com/login?qlik-web-integration-id=" + webIntegrationId + "&returnto=" + top.location.href;
              throw new Error('not logged in');
            }
          });
        }
    	login()
      </script>
    </head>
    
    <body style="height:600px;">
    	<iframe
        src="https://yourtenant.eu.qlikcloud.com/single/?appid=9539b869-1c84-4e6d-9129-4c5b031ca88a&obj=WJhPv&opt=ctxmenu,currsel"
        style="border:none;width:100%;height:100%;"></iframe>
    </body>
    
    </html>​

    
    
    
12. Paste it into a new file using Visual Studio Code and save it with the HTML extension
13. Replace all mentions of yourtenant in the script with the name of your Qlik Sense SaaS tenant
14. Copy the Web Integration ID from the Web Integration menu and paste it into the script at:
    

    const webIntegrationID = "IDGOESHERE";​

15. Add the link to the Qlik App Object you want to embed in the <iframe> section:
    

    <iframe>src="linktotheobjecthere"></iframe>

16.  Save the file and place it where your web server can read it. 

Can deleted Qlik Cloud apps or sheets be recovered? Can apps, sheets, or automations owned by a deleted user be recovered?

Once an app or sheet has been deleted it cannot be recovered.

What about deleted users and their orphaned objects?

Orphaned apps (created when the user has been deleted) can be reassigned. See Qlik Cloud Analytics: Can the owner of orphaned Apps be changed after the owner is deleted? for instructions.

For more information about what to consider before deleting a user, see Deleting users.

The following cannot be recovered:

• A deleted app
• A deleted sheet
• Personal objects belonging to a deleted user
• Automations belonging to a deleted user

Qlik suggests the following techniques to ensure no work is lost:

• Duplicate the app to the same or different 'Shared' or 'Personal' space
• Setup a test or 'recycle bin' space where duplicated apps are kept until it has been verified that the app can be fully deleted
• If space is a concern, export the app without data and re-import it to the 'recycle bin' space. This will allow you to keep an empty master copy of the app

Qlik has received feedback in the past to implement a recovery feature: Recycle bin for SaaS editions of Qlik Sense (#279017) (Log in to Qlik Ideation to leave comments and vote.)

You may encounter this issue when retrieving data from an Excel file and converting it into a CSV file using a dynamic schema. If a column contains the value “#N/A” in the Excel file, Talend reads it and returns “ERROR:#N/A” instead of the original value.

This article briefly introduces How to Handle'#N/A' Values and Preserve Original Data in Dynamic Schema Conversions in Talend.

Workaround 1: Using "User mode" for the "Generation mode", if the Excel file is not too large or if memory resources are sufficient. In this mode, it will output an empty string for cells with "#N/A."

Workaround 2: Using a tMap component after tFileInputExcel to convert the "ERROR: #N/A" column values to empty strings.

Microsoft Excel uses the #N/A function to define empty cells in order to ensure that any calculations excluding those specific cell values.

By using either of these workarounds, the empty string in the output CSV will serve as the equivalent of '#N/A' in the input Excel file.

Related Content

tMap related topics

Environment

Talend Data Integration 

If users are behind a proxy, the Qlik Web Connector may return the following errors:

• 407 proxy authentication errors and
• 503 Service Unavailable

Environment:

Qlik Web Connectors 

Under these circumstances, the user has to configure the proxy from the deploy.config file, which is normally located in the root of your Qlik Web Connectors folder.

Disabling the proxy:

This is the best approach for Error 503 Service Unavailable errors. 

Open the deploy.config file, search for Proxy in order to locate the settings and configure them as below.

<Proxy>
    <UseProxy>false</UseProxy>
    <ProxyAddress></ProxyAddress>
    <ProxyUsername></ProxyUsername>
    <ProxyDomain></ProxyDomain>
    <ProxyPassword></ProxyPassword>
</Proxy>
 

Configuring the proxy - Setting it up to true:

This is the best approach for 407 proxy authentication errors. 

If you are behind a proxy you will just need to set UseProxy to true and you might need to enter the proxy credentials as below.

<Proxy>
    <UseProxy>true</UseProxy>
    <ProxyAddress>proxy.sub-domain.mymaindomain.com:port</ProxyAddress>
    <ProxyUsername>username</ProxyUsername>
    <ProxyDomain></ProxyDomain>
    <ProxyPassword>password</ProxyPassword>
</Proxy>

When clicking the Deploy button, the data service task displays an error stating 'Feature (JOB_NAME)-feature/0.1.0 is already installed', thereby preventing the deployment of the data service.

Cause

The status of the Talend Runtime task is displaying an unsynchronized status with TMC, requiring manual work to restore the status.

Resolution

1. Login to Talend Runtime, check for the unsynchronized status task, and then stop and uninstall it.

   bundle:list |grep -i <artifact-name>
   bundle:uninstall <artifact-name>
   kar:list |grep -i <artifact-name>
   kar:uninstall <artifact-name>

2. Redeploy the data service from the TMC page.

Environment

• Talend Cloud 

It is not possible to set up a Microsoft Office 365 email provider with OAuth 2.0 authentication.
The HAR file shows this message in Network:

{connectionFailed: true, message: "Error during email request", success: false}
connectionFailed: true
message: "Error during email request"
success: false

Resolution

Configure the Mail.Send permission as it is described in Configuring a Microsoft 365 email provider using OAuth2.

Cause

This problem occurs when the Mail.Send permission has not been configured in the app registration.

Related Content

More information about the  Mail.Send permission can be found in Application permission to Microsoft Graph (learn.microsoft.com).

Environment

• Qlik Tabular reporting
• Qlik Cloud