# Talend Management Console

## New features

| Feature | Description |
| --- | --- |
| New search box | You can find the new search box in the Owner field<br>when adding or editing a space and in the Space field when<br>using the copy/move feature. |
| New design in the Metrics tab | In the Metrics tab of the Run<br>overview page, the new table format allows you to show, hide, or<br>resize columns easily. |
| Long-running task execution notifications | Users with the Operator role now receive email<br>notifications when a Job (including big data Jobs) or pipeline task has been running for more<br>than 24 hours. The notification is sent per space and repeats every 24 hours<br>until the task completes or stops. This is a mandatory notification that is<br>automatically enabled. To disable it, modify the<br>duration threshold (default: 24 hours), or adjust the notification repeat<br>frequency (default: 24 hours), contact Qlik Support. |
| Artifact publishing safeguard | Talend Management Console<br>has implemented built-in protection against ZIP attacks such as ZIP Slip, ZIP<br>Symlink, or denial-of-service attacks during Job archive publication.<br><br>For<br>details, see [Archive security restrictions when publishing<br>Jobs to Talend Cloud](https://help.qlik.com/talend/en-US/management-console-user-guide/Cloud/artifact-archive-security-restrictions-in-talend-cloud). |

## Notable fixes

| Issue | Description |
| --- | --- |
| TMC-9202 | When downloading run history as a CSV file, the apiVersion column header was absent from the exported file. This caused a mismatch between the number of column headers and the number of data columns. |
| TMC-9023 | When publishing Jobs with the Accelerate publish<br>checkbox enabled, the SHA-1 checksum was computed on the encrypted Job archive<br>instead of the original one. This caused the Talend Remote Engine or Cloud Engine to log a checksum validation warning. Job execution was not<br>affected. |
| TMC-8887 | When retrieving run logs for tasks that generated more than 100,000 log<br>lines within a single minute, the X-Log-Next-Request-End-Time<br>response header returned the same timestamp on each paginated response. As a<br>result, run logs did not load completely and were stuck in an infinite<br>loop. |