> For the complete documentation index, see [llms.txt](https://docs.helmut.de/helmut4-releases/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.helmut.de/helmut4-releases/v4.6.2/release-notes/whats-new.md).

# What's New

## These are the highlights of our Helmut release 4.6.2:

#### New features

* Added Autosync option to Cosmo Change Asset Metadata Action node

#### Improvements

* Implemented the missing lockout mechanism to lock an account after a certain number of failed login attempts
* Addressed security issues and resolved some security vulnerabilities

#### Bug fixes 

* Fixed password validation issue when creating a user, which displayed incorrect mismatch.
* Fixed the issue of the last project not being displayed in the CO tab of the Helmut4 panel.
* Fixed an issue in the Helmut4 panel extension where it was not possible to change the project after cosmo asset sync.
* Fixed the unresolved notification when renaming a user.
* Fixed the issue where the Premiere Open Choose Dialog Action node did not recognize the cancel event and ran into a timeout.
* Fixed the issue where the HTTP Request node was overriding the Content-Type.
* Fixed the ascending/descending sorting issue of the date format and file size in the dashboard.
* Fixed the polling interval issue while switching between Helmut4 products.
* Fixed the issue of "\n" being escaped within a file path – Hiscale.
* Fixed the error that occurred with special characters in metadata and folder file/directory names.

\
Various other bug fixes and performance improvements.<br>

For more detailed information check our [Changelog](/helmut4-releases/v4.6.2/release-notes/changelog.md)\
\
Please feel free to contact our Helmut Support Team in case of any questions! [Support](/helmut4-releases/v4.6.2/support/requesting-support.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.helmut.de/helmut4-releases/v4.6.2/release-notes/whats-new.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.