Skip to main content Skip to complementary content

Talend Management Console

New features

Feature Description
New execution status The Misfired status has been added to the execution statuses for tasks and plans.

The Misfired status indicates that a task or plan cannot start due to an issue. This is different from failures during executions, which are reflected under the Failed status.

This new status is not applicable to Routes or data service tasks or plans, for which the issues are still shown as Failed.

Keep in mind that the Misfired notification becomes active about one hour after the release. If you had already enabled notifications for Failed before the release, the Misfired notification is automatically enabled for you. After the release, the Failed notification and the Misfired notification are managed independently and no longer affect each other.

For further information about enabling notifications on misfired tasks or plans, see Email notifications.

Run history page with the Misfired status.
Notification email address As announced in the R2024-08 release, Talend Management Console now sends notifications from noreply@qlik.com instead of noreply@talend.com, and the sender name has also changed from Talend Cloud Notification to Qlik Talend Cloud Notification.

Deprecated and removed items

Feature Description
Support for SHA-1 (Secure Hash Algorithm 1) in Cloud Engine The support for SHA-1 in Cloud Engine is deprecated starting with the R2024-09 release and will be fully removed in the R2024-12 release.

To prepare for this change, ensure that your TLS certificates no longer use the SHA1WithRSA signature algorithm.

API version removal

API versions prior to 2.6 have been removed from Swagger in all data center regions, for example, https://api.us.cloud.talend.com/tmc/swagger/swagger-ui.html.

Additionally, API version 2.6 has been deprecated since R2024-03 and will be removed in release R2025-09.

To avoid any disruptions, migrate your API requests to the latest version. For migration instructions, see migrate your API requests.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – please let us know!