> For the complete documentation index, see [llms.txt](https://community-test.logicnets.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://community-test.logicnets.com/release-9/platform-documentation/process-node-parts/unlock-current-session.md).

# Unlock Current Session

## Description

By default, LogicNets does not process multiple requests in parallel for one session, so some requests may be delayed because the session is locked. In some cases, however, especially for GET API calls, it is not necessary to lock the session because the call is only retrieving data and not modifying the session. You can put this part at the start of the endpoint logicnet that implements the API call and the system unlocks the session and processes other session requests. When the system performs multiple calls, this helps prevent the system from waiting on locked sessions.

**Node Type:** This part is located in process nodes under the Apps menu.

**Used With:** API Functionality

## Editor Fields

| Field Name                   | Description/Use                                                                                               | Type/Options | Optional/Mandatory |
| ---------------------------- | ------------------------------------------------------------------------------------------------------------- | ------------ | ------------------ |
| Allow database write actions | Select from the dropdown whether you want the system to unlock the current session and write to the database. | No \| Yes    | Mandatory          |


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://community-test.logicnets.com/release-9/platform-documentation/process-node-parts/unlock-current-session.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.