This article explains how to obtain a task schedule in the Talend Management Console, how to pause it, and how to resume it. All steps are performed using the API.

In the example, we use the following values:

• The Environment ID: 5b0431e2ee7c2b4082797c73
• Task ID: 698ba125c327f6c153585c67
• %TOKEN% is to be replaced by your actual bearer's token
• The API URL used in each example is set to the EU region, api.eu.cloud.talend.com. Update the region accordingly. 
• The schedule is set from: 1772628971000 to 1775220971000, which is the 3rd of March 2026 to the 3rd of April 2026 in milliseconds since January 1st 1970. Use epochconverter.com to convert date and time to epoch time. 

Content

• Getting a task schedule
• Pausing a task
• Resuming a task
• Pausing and resuming a plan

Getting a task schedule

First, we get the scheduling of a task. 

The following Qlik Talend API can be used to retrieve the executions scheduled in a time window using the "from" and "to" parameters: Get scheduled executions 

Get scheduled executions of all types

POST /orchestration/executables/events/search

Example: 

curl -v -X POST ^
-H  "Content-Type: application/json" ^
-H  "Accept: application/json" ^
-H  "Authorization: Bearer %TOKEN%" ^
-d "{\"environmentId\":\"5b0431e2ee7c2b4082797c73\",\"from\":\"1772628971000\",\"to\":\"1775220971000\"}" ^
https://api.eu.cloud.talend.com/orchestration/executables/events/search

The API returns a maximum of 100 entries by default. The parameter "offset" can be used to retrieve the next entries.

Example with "offset": 

curl -v -X POST ^
-H  "Content-Type: application/json" ^
-H  "Accept: application/json" ^
-H  "Authorization: Bearer %TOKEN%" ^
-d "{\"environmentId\":\"5b0431e2ee7c2b4082797c73\",\"from\":\"1772628971000\",\"to\":\"1775220971000\",\"offset\":100}" ^
https://api.eu.cloud.talend.com/orchestration/executables/events/search

To retrieve all the entries, increase the "offset" value to the total value returned by the call that is lower than the limit value.

Pausing a task

Next, we pause the task.

The following Qlik Talend API can be used to pause a task: Pause / Resume a Task

Pause / Resume a Task

PUT /orchestration/executables/tasks/{taskId}/pause

Example:

curl -v -X PUT ^
-H  "Content-Type: application/json" ^
-H  "Accept: application/json" ^
-H  "Authorization: Bearer %TOKEN%" ^
-d "{\"pause\":true,\"pauseContext\":\"Pause during the maintenance window\"}" ^
https://api.eu.cloud.talend.com/orchestration/executables/tasks/698ba125c327f6c153585c67/pause

Resuming a task

We now set the task to resume.

The following Qlik Talend API can be used to resume a task: Pause / Resume a Task

Pause / Resume a Task

PUT /orchestration/executables/tasks/{taskId}/pause

Example:

curl -v -X PUT ^
-H  "Content-Type: application/json" ^
-H  "Authorization: Bearer %TOKEN%" ^
-d "{\"pause\":false}" ^
https://api.eu.cloud.talend.com/orchestration/executables/tasks/698ba125c327f6c153585c67/pause

Pausing and resuming a plan

To pause and resume a plan, the following Qlik Talend API can be used: Pause-Resume Plan executions

Pause-Resume Plan executions

PUT /orchestration/executables/plans/{planId}/pause

Environment

• Qlik Talend Cloud
• Qlik Talend Management Console

When attempting to execute a Talend Management Console (TMC) task using a Service Account via the Talend Management Console API, users may encounter an HTTP 403 Forbidden response—even if the Service Account is correctly configured.

When attempting to execute a task using the Processing API endpoint:

POST https://api.<region>.cloud.talend.com/processing/executions

the API returns:

 

{  "status": 403,  "requestId": "5303a858-8849-4572-ad37-4ce42c077c41",  "message": "Forbidden" }

This issue typically arises when the necessary permissions for task execution are not granted prior to generating the service account token, or when the service account lacks specific functional permissions pertaining to task execution.

Observed behavior

The token generated via:
POST /security/oauth/token
is valid.

The Service Account permissions appear to include:

TMC_ENGINE_USE
TMC_ROLE_MANAGEMENT
TMC_SERVICE_ACCOUNT_MANAGEMENT
AUDIT_LOGS_VIEW
TMC_USER_MANAGEMENT
TMC_CLUSTER_MANAGEMENT

According to the documentation Using a service account to run tasks | Qlik Help Center, the Service Account must possess either TMCENGINEUSE or TMC_OPERATOR permissions; however, even with these permissions, the execution still fails.

Resolution

Step 1: Assign "Tasks and Plans – Edit" Permission

Navigate to Talend Management Console→ Users & Security → Service Accounts, and ensure the Service Account has the permission: Tasks and Plans – Edit

Step 2: Regenerate the Service Account Token

After updating permissions, regenerate service account Token.

This ensures that the token contains the updated permission set. Subsequently, rerunning the task via the API will work.

Environment

• Talend Cloud 

To retrieve the task with the status "Misfired" via API, you can use the API "/monitoring/observability/executions/search" mentioned below:

#type_searchrequest | talend.qlik.dev .

However, EXECUTION_MISFIRED status returned only if "exclude=TASK_EXECUTIONS_TRIGGERED_BY_PLAN"

So if you want to return any plans or tasks that are misfired, you should send this filter request:

 "filters": [  {  "field": "status",  "operator": "in",  "value": [  "DEPLOY_FAILED",  "EXECUTION_MISFIRED"  

Example

URL: https://api.<region>.cloud.talend.com/monitoring/observability/executions/search

{
    "environmentId": "123456......",
    "category": "ETL",
    "filters": [
        {
            "field": "status",
            "operator": "in",
            "value": [
                "DEPLOY_FAILED",
                "EXECUTION_MISFIRED"
            ]
        }
    ],
    "limit": 50,
    "offset": 0,
    "exclude": "TASK_EXECUTIONS_TRIGGERED_BY_PLAN"
}

Internal Investigation ID(s) 

Jira ID: SUPPORT-7251

Environment

• Talend ESB 
• #Talend Cloud API

The Talend Cloud Management Console Public API enables users to manage Talend Management Console (TMC) from an external system (for example, a scheduler, script, or program).

Environment

This article uses Talend Cloud API 1.2, which supports operations for tasks, plans, and promotions in Talend Cloud. Note: Talend Cloud API 1.1 only supports operations on tasks, and version 1.0 has been deprecated.

Content:

• Prerequisites
• Executables and executions
• Generating a token
• API operations for tasks in Talend Cloud
• Get available Tasks - /executables
• Get Task details - /executables/{id}
• Execute Task - /executions
• Terminate Task execution - /executions/{id}
• Get Task execution status - /executions/{id}
• API operations for plans in Talend Cloud
• Get available Plans - /executables/plans
• Get Plan details - /executables/plans/{id}
• Execute Plan - /executions/plans
• Get Plan execution status - /executions/plans/{id}
• API operations for promotions in Talend Cloud
• Get available Promotions - /executables/promotions
• Get Promotion details - /executables/promotions/{id}
• Execute Promotion - /executions/promotions
• Get Promotion execution status - /executions/promotions/{id}
• Conclusion

Prerequisites

• Talend Cloud subscription
• Talend Cloud Management Console access credentials (can also be used to access API)

Executables and executions

A list of supported operations is available on the API documentation page. There are three URLs, each for a different region of Talend Cloud. However, the list of operations does not vary by region.

• US: https://api.us.cloud.talend.com/tmc/

• EU: https://api.eu.cloud.talend.com/tmc/

• APAC: https://api.ap.cloud.talend.com/tmc/

The API operations consist of executables and executions, with a separate set of operations available for each.

• Operations related to executables use the GET method to get information about executables, such as tasks, plans, and promotions.
• Operations related to executions perform actions such as execute or terminate using the POST, DELETE, or GET method.
• Supported operations on executables get lists of tasks, plans, or promotions, as well as details for these by ID, for instance, using "Get task details by task ID".
• The POST method is used for an operation that supports execution of a task, plan, or promotion.
• The DELETE method is used for deleting a task.

Generating a token

The first step in using the API is generating a personal access token; then you can start managing TMC through the API. Follow the detailed steps for Generating a personal access token in the Talend Help Center. You get a token that looks like this:

As mentioned in the help, you can use this token for authorization, for example in a curl command:

curl -X GET 'https://api.us.cloud.talend.com/tmc/v1.2/executables' \
-H 'Authorization: Bearer eyJraWQiOiJpYW0tb2lpYy1jbG91ZCIsImQu2WembcCB'

This article references the Swagger UI available as part of API documentation authorization; it uses email and password login credentials instead of a token.

API operations for tasks in Talend Cloud

Here are the operations available for accessing a task or its details, and for managing task execution:

Here are details on how to perform each operation with different scenarios:

Get available Tasks - /executables

/executables lists available tasks in all environments using the GET method.

The HTTPS URL for this operation is https://api.eu.cloud.talend.com/tmc/v1.2/executables.

To try this in the Swagger UI:

1. Click the name of the operation to expand it.
2. Click the Try it out! button.

Notice that /executables is highlighted in the Curl and Request URL sections:

The Response Body section lists all tasks in all environments of the Talend Cloud subscription. In this operation, a Response Code of 200 indicates that the API call is successful.

Get Task details - /executables/{id}

To get task details by task ID instead of getting all tasks, you use the /executables/{id} operation. The HTTPS URL for this operation is https://api.eu.cloud.talend.com/tmc/v1.2/executables/5c275067e91341357ef0b86b.

Execute Task - /executions

To execute a task, use /executions and specify the execution ID. In the example below, the parameter required for execution is the executable ID. In this case, the task is executable. Specify the parameter in JSON format. The response is the execution ID.

You can verify the execution logs in TMC by opening the task and viewing the run history. The execution ID returned as part of Response Body is used to find the execution. The screenshot shows the log for the sample task execution:

Terminate Task execution - /executions/{id}

To terminate a task in execution, use /executions/{id} called using the DELETE method. For example, in the Swagger UI as below, using the f88b8a8f-4a51-4ac5-9453-2c8eaf1e01a4 execution ID returned as part of a previous request (in the Execute Task example) terminates task execution. Because task execution in the previous API call was successful, the response returned for this terminate operation is Nothing to do for the task: its status is EXECUTION_SUCCESS.

In a real-world scenario, the terminate task would help stop execution of any long-running task.

Get Task execution status - /executions/{id}

Before terminating a task, calling /executions/{id} using the GET method returns the status of the task. This operation of getting the execution status by ID tells you whether the task is in progress, has been completed, or has failed. In the screenshot below, for the f88b8a8f-4a51-4ac5-9453-2c8eaf1e01a4 sample execution ID, notice the detailed status returned by the operation as part of Response Body:

API operations for plans in Talend Cloud

Get available Plans - /executables/plans

Like tasks, the cloud API allows you to manage plans externally. A plan is the step-by-step execution of one or more tasks. To list all plans created in all environments, the request URL, submitted using the GET method, is https://api.eu.cloud.talend.com/tmc/v1.2/executables/plans. Response Body lists plans in JSON format:

Get Plan details - /executables/plans/{id}

To get details on a particular plan using the executable ID, the request URL, submitted using a GET method, is https://api.eu.cloud.talend.com/tmc/v1.2/executables/plans/{id}. In this example, the executable ID is 49fe0c6d-95e8-413c-aa97-13a15e506350, so the request URL is https://api.eu.cloud.talend.com/tmc/v1.2/executables/plans/49fe0c6d-95e8-413c-aa97-13a15e506350.

The response for this operation consists of detailed plan information in JSON format:

Execute Plan - /executions/plans

To execute a plan from an external system, the request URL format is https://api.eu.cloud.talend.com/tmc/v1.2/executions/plans. This URL is submitted using the POST method. The parameter required for this operation consists of an executable ID in JSON format:

Just as with a task execution using the POST method, a plan execution returns an execution ID as the response. A plan execution generates logs for every task in the steps in the plan:

Get Plan execution status - /executions/plans/{id}

To get the execution status of a plan, the request URL format is https://api.eu.cloud.talend.com/tmc/v1.2/executions/plans/{id}. For this example, the request URL is https://api.eu.cloud.talend.com/tmc/v1.2/executions/plans/67975122-8e92-4b81-8818-6ce161763ece.

Response Body contains detailed information about the plan execution:

API operations for promotions in Talend Cloud

Get available Promotions - /executables/promotions

To get a list of all promotions, the request URL is https://api.eu.cloud.talend.com/tmc/v1.2/executables/promotions. Whether it is a list of promotions, tasks, or plans, the API call returns the response based on the credentials or token permissions (based on user access). This screenshot shows the sample get available promotions operation:

Get Promotion details - /executables/promotions/{id}

You can get the details of a promotion from the executable ID. Notice the highlighted Request URL and Response Body sections:

Execute Promotion - /executions/promotions

For the execute promotion operation, the request URL is https://api.eu.cloud.talend.com/tmc/v1.2/executions/promotions, called using a POST method that requires a JSON parameter:

{
 "executable": "5ce39250b0daaa43cfc64271",
 "keepTargetResources": true,
 "advanced": {
   "artifactId": "5d5bc62796184c43f45d310e",
   "artifactType": "ACTION"
 }
}

The value for artifactType in the JSON parameter determines the scope of the promotion. Refer to Managing promotions in the Talend Help Center for details about promoting artifacts, tasks, plans, workspaces, and environments.

The ACTION value promotes an artifact.

You are ready to explore the execute promotion operation in more detail. For the promotion in this article, the source environment is Vpdev and the target environment is VPProd. An artifact is promoted using artifact ID 5d5bc62796184c43f45d310e in the VPdev environment:

The target environment does not have this artifact before executing the promotion:

When you execute the promotion, Response Body for the execute promotion operation contains the execution ID:

The artifact has been promoted:

Get Promotion execution status - /executions/promotions/{id}

Using the execution ID returned as the response with the previous execute promotion operation, you can obtain the execution status of another operation, Get Promotion execution status. The request URL format is https://api.eu.cloud.talend.com/tmc/v1.2/executions/promotions/{id}. For example, the URL for the execution ID in the previous operation is https://api.eu.cloud.talend.com/tmc/v1.2/executions/promotions/5d5c0223780a65440e3fed53:

Conclusion

You have learned how to use the Talend Cloud Management Console Public API to manage tasks, plans, and promotions from an external system. You can use either a personal access token or Talend Cloud access credentials. The best practice is to use a personal access token to manage Talend Cloud tasks, plans, and promotions. Performing a combination of operations through the API is ideal for most use cases that require external management.

In Qlik Sense Enterprise on Windows, using QRS API '/qrs/App/table' by providing a body returns more than expected rows. 

Example: 

1. Using POSTMAN, we perform a POST call including the body:
   
   
   
   
2. With the above body, we expect that the response rows would ONLY contain name, id, and values as defined above in "list":
   
   
   
   
3. However, this POST request returns more than the requested rows, such as id, name, valueType, choiceValues, and privileges:
   
   

Resolution

This behavior has been identified as defect SUPPORT-6127.

It is caused by the default value of the parameter HideCustomPropertyDefinition set to true in the Repository.exe.config file. Changing the parameter from true to false resolves it.

To change the value: 

1. Navigate to C:\Program Files\Qlik\Sense\Repository\ and locate Repository.exe.config
2. Open Repository.exe.config in a text editor
3. Find HideCustomPropertyDefinition and set its value from true to false
   If you are running a multi node environment, make the change on each node. 
4. Save the Repository.exe.config file‘false’

Cause

Issue related to the default configuration setting of the parameter HideCustomPropertyDefinition in the Repository.exe.config file.

Internal Investigation ID(s)

SUPPORT-6127

Environment

• Qlik Sense Enterprise on Windows

When Stitch replicates data from SaaS sources, it must operate within the API rate limits defined by each vendor. These limits determine how many API requests can be made within a specific time period to prevent server overload. Exceeding them typically results in rate limit errors (most often HTTP 429 responses), which can temporarily interrupt data replication.

This article outlines common API rate limit errors observed in Stitch integrations and provides best practices to help you minimize and handle these limits for reliable data replication.

Known API Rate Limit Errors

The exact error message for exceeding API rate limits varies across platforms, but all indicate the same underlying cause — too many API requests made within a defined time window.

Refer to the table below for examples of rate limit errors observed in popular Stitch SaaS integrations | Stitch Documentation:

Stitch recommendations & solutions for rate limit errors

• Reduce replication frequency of an integration if extractions frequently exceed the API’s rate limit.

• Stagger replication frequency schedules for multiple integrations that connect to the same source account to reduce the number of concurrent calls.

• Use the key-based incremental replication method | Stitch Documentation where available:
  
  Full Table Replication: Extracts all data from the Start Date indicated in the integration settings during every extraction. This usually requires many API calls as most integrations use pagination to retrieve data.
  Incremental Replication: Only fetches new or changed records since the last successful sync, based on a bookmark value. 
  Incremental replication can reduce API call volume by extracting less data, thereby reducing the number of API calls that would need to be made.

• Monitor extraction logs in Stitch for frequent 429 errors.

• Contact the API provider to request increased rate limits where applicable.

• Contact Qlik Support if needed.

Environment

• Stitch 

During the extraction process of your HubSpot integration, the following error was encountered:

requests.exceptions.HTTPError: 500 Server Error: Internal Server Error for url <CustomURL>

...

Giving up on request after {} tries with url {} and params {}

Resolution

This error may be transient. However, if it is recurring frequently enough to disrupt your workflow, please reach out to Qlik Support.

Cause 

The HubSpot API is having issues processing the amount of data compiled based on the request sent by Stitch.

Environment

• Stitch 

Question

How can we retrieve artifact information from Talend update website? For instance, for artifact "accessors-smart-2.4.11.jar", we can use the following URL to query its information: https://search.maven.org/solrsearch/select?q=a:accessors-smart+AND+v:2.4.11&rows=1&wt=json

Does Talend also offer a similar feature for its artifacts?

Answer

Talend update website is built on Nexus and utilizes the Lucene search API, as demonstrated in the following example:

https://talend-update.talend.com/nexus/service/local/lucene/search?a=accessors-smart&v=2.4.11

For further details on the Lucene search API, please refer to: Nexus Indexer Lucene Plugin REST API | repository.sonatype.org

Environment

• Talend Data Integration 

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 

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 

Qlik Automate is a no-code automation and integration platform that lets you visually create automated workflows. It allows you to connect Qlik capabilities with other systems without writing code. Powered by Qlik Talend Cloud APIs, Qlik Automate enables users to create powerful automation workflows for their data pipelines.

Learn more about Qlik Automate.

In this article, you will learn how to set up Qlik Automate to deploy a Qlik Talend Cloud pipeline project across spaces or tenants.

To ease your implementation, there is a template on Qlik Automate that you can customize to fit your needs.
You will find it in the template picker: navigate to Add new → New automation → Search templates and search for ‘Deploying a Data Integration pipeline project from development to production' in the search bar, and click Use template.

ℹ️ This template wil be generally available on October 1, 2025.

Use case and pre-requisites

In this deployment use case, the development team made changes to an existing Qlik Talend Cloud (QTC) pipeline.

As the deployment owner, you will redeploy the updated pipeline project from a development space to a production space where an existing pipeline is already running.

To reproduce this workflow, you'll first need to create:

• Two data spaces:
• A DEV space
• A PROD space
• Two source databases
• A DEV source database
• A PROD source database
• Two target databases
• A DEV target database
• A PROD target database

Using separate spaces and databases ensures a clear separation of concerns and responsibilities in an organization, reduces the risk to production pipelines while the development team is working on feature changes.

Workflow steps:

1. Export the updated pipeline project from the DEV space
2. Get the project variables from DEV
3. Update the project variables for PROD before import
4. Stop the pipeline currently running in production
5. Import your project to the PROD space
6. Prepare your project and check the status
7. Restart the project in PROD

ℹ️ Note: This is a re-deployment workflow. For initial deployments, create a new project prior to proceeding with the import.

Step-by-step workflow

1. Export the updated pipeline project from the DEV space

Use the 'Export Project' block to call the corresponding API, using the ProjectID.

This will download your DEV project as a ZIP file. In Qlik Automate, you can use various cloud storage options, e.g. OneDrive. Configure the OneDrive 'Copy File on Microsoft OneDrive' block to store it at the desired location.

To avoid duplicate file names (which may casue the automation to fail) and to easily differentiate your project exports, use the 'Variable' block to define a unique prefix (such as dateTime). 

2. Get the project variables from DEV

From the 'Qlik Talend Data Integration' connector, use the 'Get Project Binding' block to call the API endpoint.

The 'bindings' are project variables that are tied to the project and can be customized for reuse in another project. Once you test-run it, store the text response for later use from the 'History' tab in the block configuration pane on the right side of the automation canvas:

3. Update the project variables for PROD before import

We will now use the 'bindings' from the previous step as a template to adjust the values for your PROD pipeline project, before proceeding with the import.

From the automation, use the 'Update Project Bindings' block. Copy the response from the 'Get Project Binding' block into the text editor and update the DEV values with the appropriate PROD variables (such as the source and target databases). Then, paste the updated text into the Variables input parameter of the 'Update Project Binding' block.

ℹ️ Note: these project variables are not applied dynamically when you run the 'Update Bindings' using the Qlik Automate block. They are appended and only take effect when you import the project.

4. Stop the pipeline currently running in production

For a Change Data Capture (CDC) project, you must stop the project before proceeding with the import.

Use the 'Stop Data Task' block from the 'Qlik Talend Data Integration' connector. You will find the connectors in the Block Library pane on the left side of the automation canvas.

Fill in the ProjectID and TaskID:

ℹ️ We recommend using a logic with variables to handle task stopping in the automation. Please refer to the template configuration and customize it to your needs.

5. Import your project to the PROD space

You’re now ready to import the DEV project contents into the existing PROD project.

⚠️ Warning: Importing the new project will overwrite any existing content in the PROD project.

Using the OneDrive block and the 'Import Project' blocks, we will import the previously saved ZIP file.

ℹ️ In this template, the project ID is handled dynamically using the variable block. Review and customize this built-in logic to match your environment and requirements.
 

After this step is completed, your project is now deployed to production.

6. Prepare your project and check the status

It is necessary to prepare your project before restarting it in production. Preparing ensures it’s ready to be run by creating or recreating the required artifacts (such as tables, etc).

The 'Prepare Project' block uses the ProjectID to prepare the project tasks by using the built-in project logic. You can also specify one or more specific tasks to prepare using the 'Data Task ID' field. In our example, we are reusing the previously set variable to prepare the same PROD project we just imported.

If your pipeline is damaged, and you need to recreate artifacts from scratch, enable the 'Allow recreate' option. Caution: this may result in data loss.

Triggering a 'Prepare' results in a new 'actionID'. This ID is used to query the action status via the 'Get Action Status' API block in Qlik Automate. We use an API polling strategy to check the status at a preset frequency. 

Depending on the number of tables, the preparation can take up to several minutes.

Once we get the confirmation that the preparation action was 'COMPLETED', we can move on with restarting the project tasks.

If the preparation fails, you can define an adequate course of action, such as creating a ServiceNow ticket or sending a message on a Teams channel.

ℹ️ Tip: Review the template's conditional blocks configuration to handle different preparation statuses and customize the logic to fit your needs.

7. Restart the project in PROD

Now that your project is successfully prepared, you can restart it in production.

In this workflow, we use the 'List Data Tasks' to filter on 'landing' and 'storage' for the production project, and restart these tasks automatically.

All done: your production pipeline has been updated, prepared, and restarted automatically!

Now it’s your turn: fetch the Qlik Automate template from the template library and start automating your pipeline deployments.

Related Content

About Qlik Automate

Start a Qlik Talend Cloud® trial

How to get started with the Qlik Talend Data Integration blocks in Qlik Automate

How to use the Qlik Automate templates

NPrinting has a library of APIs that can be used to customize many native NPrinting functions outside the NPrinting Web Console.

Environment:

Qlik NPrinting 

An example of two of the more common capabilities available via NPrinting APIs are as follows

• Connection reloads
• Publish Task executions

These and many other public NPrinting APIs can be found here: Qlik NPrinting API

In the Qlik Sense data load editor of your Qlik Sense app, two REST connections are required (These two REST Connectors must also be configured in the QlikView Desktop application>load where the API's are used. See Nprinting Rest API Connection through QlikView desktop)

• GET
• POST

Requirements of REST user account:

• Windows Authentication is required in both these connectors. The required user account is the NPrinting service account (which is also ROOTADMIN on the Qlik Sense server)
• This user account must also be a member of the NPrinting 'Administrators' Security Role on the NPrinting Server.

Creating REST "GET" connections

Note: Replace QlikServer3.domain.local with the name and port of your NPrinting Server

NOTE: replace domain\administrator with the domain and user name of your NPrinting service user account

Creating REST "POST" connections

Note: Replace QlikServer3.domain.local with the name and port of your NPrinting Server

NOTE: replace domain\administrator with the domain and user name of your NPrinting service user account

Ensure to enter the 'Name' Origin and 'Value' of the Qlik Sense (or QlikView) server address in your POST REST connection only.

Replace https://qlikserver1.domain.local with your Qlik sense (or QlikView) server address.

Ensure that the 'Origin' Qlik Sense or QlikView server is added as a 'Trusted Origin' on the NPrinting Server computer

Related Content

• Distribute NPrinting reports after reloading a Qlik App
• Extending Qlik NPrinting
• Run a Qlik NPrinting API POST command via QlikView reload script
• Troubleshooting Common NPrinting API Errors

NOTE: The information in this article is provided as-is and to be used at own discretion. NPrinting API usage requires developer expertise and usage therein is significant customization outside the turnkey NPrinting Web Console functionality. Depending on tool(s) used, customization(s), and/or other factors ongoing, support on the solution below may not be provided by Qlik Support.

A user's last login timestamp can be retrieved using the Qlik Audit API and filtering by the event type: com.qlik.user-session.begin

For more information, see: Audits.

The login timestamps can also be obtained from the Qlik Cloud Entitlement Analyzer app.

Environment

• Qlik Cloud Analytics

By default, the touch screen function cannot be disabled in Qlik Sense Enterprise on Windows. It is enabled whenever the client recognizes a touch-enabled device, such as a mobile phone or tablet. 

It can be disabled manually by the user, but not globally on the server.

To disable Touch Screen mode manually:

1. Click the three dots (ellipsis) in the top left corner
2. Toggle Touch  Screen Mode on or off
   
   

An idea has been created to gather demand on allowing this feature to be disabled on server/administration level. See Option to Disable Touch Screen or toggle Touch Screen off on server side.

Environment:

Qlik Sense Enterprise on Windows 

It is possible to disable touch screen options entirely in, for example, mashups. 

A mashup can send information to the client that sends a fixed device type,  which modifies the UI accordingly.

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.

Example:

// Sets device type, which modifies the UI accordingly.
// The device type is automatically detected if it is not manually set.

@function
// String describing the device type.
@param {'auto'|'touch'|'desktop'} deviceType

@example
qlik.setDeviceType('desktop');

 More information could be found on the help site: setDeviceType method

The older API user accounts, which are no longer accessible due to team members departing or their email addresses becoming inactive, are currently unavailable. Consequently, you are unable to manage or update these APIs, as the original owners are absent, and you lack the authority to edit and publish new versions.
For all newly defined APIs, you have the capability to directly assign ownership to the "Architects" group. However, regarding the existing APIs, you are unable to alter their ownership on your own.

Resolution

Talend Cloud API Designer allows you to share APIs with other users and/or groups of users. For additional details, please refer to the sharing api documentation.

Note:  In the Talend Cloud API Designer settings, it is possible to reassign API contracts previously created by deleted users to active connected users. This option is only available for users that have the Administrate API Designer permission enabled.

Environment

• Talend Cloud API Designer & Tester

Deploying an app with Qlik CLI from Git (with app unbuild and app build ) fails when using the --bookmark parameter. 

Resolution

• Verify that the app contains the bookmarks. If the source app has bookmarks, they will be included in the building process. If there are no bookmarks in the source app, they will not appear in the target app. 
• Verify the syntax used:
  
  

  qlik app build --bookmark --app --git-repo

Environment

• Qlik Cloud Analytics
• Qlik CLI

When running extractions in Shopify that involve requesting a large quantity of data, encountered a ServerError.

This is notably seen during initial/historical data extractions.

Cause

Too much data is being requested from Shopify and it creates a Sever Error because Shopify is unable to process the large amount of data via their API.

Resolution

When this error arises, Stitch Subject Matter Experts have the capability to adjust a tuning parameter labeled "Results Per Page". If you encounter this error, it is advisable to consult with a Stitch Subject Matter Expert to establish an appropriate value for this parameter and thereby resolve the issue.

Environment

• Qlik Stitch

A Talend Job includes a tRest component that attempts to post 100kb of JSON/XML data to an API, but fails with the following error: 

tREST component fails with the error "400 , {
"failures": [
{
"field": "name",
"constraint": "Must be a string value, at least 1 character and at most 100 characters long."
},
{
"field": "fields",
"constraint": "Is required."
}
]
}"

Cause

When a Job includes both tRest and tRestClient components, tRest will use CXF implement auto to make HTTP requests. This will cause some random issues, as the CXF framework forces the use of the transfer-encoding header when the body size exceeds 4096. This will result in the post data being chunked (Transfer-Encoding: chunked), and then the server side cannot interpret the data fully as a whole. This was a previously identified defect. 

Resolution

To resolve this issue, a temporary workaround is to select the "Disable chunked encoding" checkbox on tRestClient.

Alternatively, apply the Studio v8-R2025-03 patch.

Internal Investigation ID(s) 

QTDI-1208

Environment

• Talend Data Integration 8.0.1

Qlik Cloud has a built-in method to export apps from your managed spaces, along with APIs available which allow for automation. 

Content:

• Export apps from Managed spaces (native method)
• Export apps using the Rest API
• Method One: REST APIs
• Method Two: Qlik-Cli:
• Unpublish an app with the REST API
• Method One: REST APIs
• Method Two: Qlik-Cli

Export apps from Managed spaces (native method)

This is the recommended method.

As of the 30th of January 2024, Qlik Cloud has introduced the functionality to Export apps from Managed Spaces.

Space Owner and users with the "Can Manage" role, can now export Qlik Cloud apps from Managed Spaces.

These apps can only be exported without data. Storytelling is not exported.

This possibility allows you to re-establish a parent - child relation of your source and published apps, in case the source app was accidentally deleted.

For more information, see:

• Exporting apps from managed spaces
• Exporting apps from Managed Spaces (Vidyard video)

Export apps using the Rest API 

You can also export the app from a managed space without data through the REST API or Qlik Cli in a supported way. 

These apps can only be exported without data, even if the NoData parameter is not set to true. Storytelling is not exported.

Method One: REST APIs

Requirements:

• PowerShell
• API keys enabled
• The App ID
• Your tenant URL

$hdrs = @{}
$hdrs.Add("Authorization","Bearer eyJhbGciOiJFUzM4NCIsImtpZCI6IjUzYj...VJaO0zSKZs7Q")
$tenanturl =  "https://yourtenant.ap.qlikcloud.com"
$appid = "7972e3ae-df5c-4ed3-81f4-e2220d76972d"
$url = $tenanturl+"/api/v1/apps/"+$appid+"/export?NoData=true"
 
$output = "C:\temp\MyExportedApp.qvf"
$firstcall=Invoke-WebRequest -Uri $url -Method Post -Headers $hdrs
 
$url2= $tenanturl+$firstcall.Headers.Location
echo $url2
Invoke-RestMethod -Uri $url2 -Method Get -Headers $hdrs -ContentType 'multipart/form-data' -OutFile $output

Reference: 

 Exports a specific app | Qlik Developer

Method Two: Qlik-Cli:

qlik app export 7972e3ae-df5c-4ed3-81f4-e2220d76972d --NoData > C:\temp\MyExportedApp.qvf

Reference:

app export | Qlik Developer

Unpublish an app with the REST API

Alternatively, an app can be unpublished from a Managed space and obtained for editing. This method maintains data, including storytelling.   

Use this method at your own risk. Direct API calls make changes which bypass safety nets and the end result can lead to unexpected results. 

Requirements:

• PowerShell
• API keys enabled
• The App ID
• Your tenant URL

Method One: REST APIs

This will move the app from a Management Space to your Personal space with the REST API.

1. Create an API key to perform the call. First of all. See https://qlik.dev/tutorials/generate-your-first-api-key
2. Using PowerShell, execute the following:
   

   [Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12
   
   $body='{"spaceId":""}'
   $hdrs = @{}
   $hdrs.Add("Authorization","Bearer eyJhbGciOiJM4ImtpZCI6IjBkZmQ5YzM2LTcy...YLmG54QLpd")
   $hdrs.Add("content-type","application/json")
   $url = "https://yourtenant.eu.qlikcloud.com/api/v1/apps/APPID/space"
   Invoke-RestMethod -Uri $url -Method Put -Headers $hdrs -Body $body

   
   Replace: 
   
   eyJhbGciOiJM4ImtpZCI6IjBkZmQ5YzM2LTcy...YLmG54QLpd with the API key you've generated
   yourtenant.eu.qlikcloud.com with your tenant URL
   APPID with your app ID 
   
   Tip: Get the App ID directly from the hub URL when you have the App open.
   
   
   
   
3. After the command is executed, the App will be moved to your personal space. This operation will retain bookmarks and sheets, though not their original owners. 

Troubleshooting:

See following article if any TLS/SLL error are output when running the PowerShell script:
Qlik Sense API: Could not create secure SSL/TLS channel (Powershell)

Method Two: Qlik-Cli

This will move the app from a Management Space to your Personal space with the REST API, wrapped in the QLIK-CLI.

Alternatively, if qlik-cli is installed, the following commands can be used. In the code, replace APPID with the correct one (e.g. 68aae8b0-3770-435d-951d-7b97469fb78b​). 

1. Set the qlik-cli user as the owner (this is necessary if you don't want the app to go the original owner's personal space, in case they have left the company):
   

   qlik app owner APPID

2. Move the app to the owner's personal space:
   

   qlik app space update APPID

3. (Optional) once moved to the personal space, create a duplicate (to use as the new source app), and put back the original app in the original space. This way, all the dependencies and links to the published app will be kept:
   

   qlik app space update APPID​ --spaceId SPACEID​

The admin using the qlik-cli commands will need to have full permissions on the Managed space that hosts the app.

Use this method at your own risk. The direct API calls used in this workaround make changes which bypass safety nets and the end result can lead to unexpected results.