Talend Management Console
Last updated: 10/30/2026Upcoming changes for UI
In R2026-11, Talend Management Console will mask the webhook URL for a task or plan trigger, displaying it as *******, for users who do not have Operator (Execute) permission on the space. Users with this permission will continue to see the full webhook URL.
For more information, see Webhooks in Talend Management Console and Generating a webhook URL.
Upcoming changes for API
In the same R2026-11 release, the run-config response returned for task and plan executables will mask the webhook trigger url as ******* for callers who do not have Operator (Execute) permission on the space. Callers with this permission will continue to receive the full URL.
Before:
{
"trigger": {
"webhook": {
"name": "wh",
"triggerCalls": 10,
"triggerTimeout": 30000,
"runAsUser": "myuser",
"runAsUserType": "HUMAN",
"url": "https://webhooks.eu.cloud.talend.com/mywebhook/<webhook-id>"
}
}
}After, for callers without Operator (Execute) permission on the space:
{
"trigger": {
"webhook": {
"name": "wh",
"triggerCalls": 10,
"triggerTimeout": 30000,
"runAsUser": "myuser",
"runAsUserType": "HUMAN",
"url": "*******"
}
}
}What you should do
If you have automation, integrations, or service accounts that read the webhook URL through the API, grant them Operator (Execute) permission on the relevant space before this change takes effect. Otherwise, they will receive the masked value instead of the webhook URL.
New features
| Feature | Description |
|---|---|
| Lineage generated for each Job task execution |
When lineage collection is enabled for a Job task, lineage is now generated for each task execution instead of only the first successful execution of a task version. This update helps ensure that lineage changes are reflected after every run in Qlik Cloud. For more information, see Enabling lineage collection for Job tasks. |
| Lineage availability shown during Job task configuration | When you create or edit a Job task, Talend Management Console shows the Allow lineage collection of this task option only for artifacts that support lineage. This helps you identify compliant artifacts before saving the task. |
| Navigation through paused tasks in Plan builder |
If a plan contains paused tasks, the plan edit view now displays a paused-task message with a navigation control to move directly to the affected step. If the full plan is visible, the view zooms in on that step to make the paused task easier to locate and review. |
| Improved processor selection in task configuration | When you create or edit a task, the wizard now uses a Processor field with a Find processors flow. You can search or filter processors by name, allocation, status, or type across engine types. |
| Asynchronous promotion analysis and execution | Two new API endpoints let you start promotion analysis or fully execute a
promotion from a previous analysis and retrieve the generated report. Use POST /processing/executions/promotions/async to analyze a promotion or execute a previously analyzed promotion. If the request returns 202, use the returned executionId with GET /processing/executions/promotions/{promotionId}/report/{executionId} to retrieve the report. After the report status is ANALYZED, submit RESUME to execute the promotion. |
Notable fixes
| Issue | Description |
|---|---|
| TMC-10104 - Run profiles remain after Talend Remote Engine cluster deletion | Deleting a cluster now also deletes its associated run profiles, preventing orphaned profiles. |
| TMC-10103 - Run profiles cannot be deleted after the associated processor or engine is deleted | You can now delete a run profile even when its associated processor or engine no longer exists. |
| TMC-10002 - Schedule or trigger changes are lost when saving and exiting from the Processing step | The task wizard now saves schedule or trigger changes made in Schedule when you click Save and Exit from Processing. |