> 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/helmut4-components/helmutfx/streams/fx-event-triggers/unlock_project.md).

# UNLOCK\_PROJECT

This trigger will activate whenever a project is being closed. When using Premiere Pro, it is crucial to ensure that the project lock action is properly configured, as it will monitor the deletion of the .prlock file upon project closure.

For additional details on the Premiere Pro project lock, please refer to the dedicated node documentation at the following link:

* [Premiere Force Native Lock Action](/helmut4-releases/helmut4-components/streamdesigner/nodes/actions/adobe-premiere-pro/premiere-force-native-lock-action.md)
* [Premiere Native Lock Action](/helmut4-releases/helmut4-components/streamdesigner/nodes/actions/adobe-premiere-pro/premiere-native-lock-action.md)

Since there is no project lock available for After Effects, the trigger will monitor the closure of the application.

### Disclaimer

{% hint style="warning" %}
When unlocking a project, please refrain from using a [Project Status Update Action](/helmut4-releases/helmut4-components/streamdesigner/nodes/actions/project-21/project-status-update-action.md) node within this stream/trigger type.

This action can potentially lead to an infinite unlocking loop, as the project status will be set to "Locked" at the end of this stream by default.

Change the project status in another stream, a profile that must be executed using a [Job Create Job Action](/helmut4-releases/helmut4-components/streamdesigner/nodes/actions/job-action/job-create-job-action.md) node.
{% endhint %}

<figure><img src="/files/mg5BHE2xPvbBDOHH561P" alt="" width="563"><figcaption><p>Index a project via a HK profile</p></figcaption></figure>


---

# 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/helmut4-components/helmutfx/streams/fx-event-triggers/unlock_project.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.