> For the complete documentation index, see [llms.txt](https://docs.soraco.co/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.soraco.co/docs/floating-licenses/cloud-floating-licenses/cloud-license-reclamation.md).

# Cloud License Reclamation

### Overview

*\[The Reclamation service described below is available as of QLM v20.0.26177.4]*

When using **QLM Cloud Licenses**, your QLM-protected application includes a built-in timer (via the `QlmCloudFloatingLicenseHelper` class) that periodically contacts the server to verify whether the license is still checked out.

### License Validation Frequency

You can control how often this validation occurs by setting the `QlmCloudFloatingLicenseHelper.QlmTimerFrequency` property.

> **Note:** For Soraco-hosted license servers, the minimum allowed validation interval is **3 hours**.

Each time a client validates a license with the server, the **Last Accessed Date** of the license is updated (requries QLM *v20.0.26177.4*).

### License Reclamation

License Reclamation relies on the **Last Accessed Date** to determine whether a license is still actively in use.

As long as your application remains open, it continues to send heartbeat signals to the server, ensuring the license is considered active. A license is typically considered inactive in scenarios such as:

* The computer is shut down
* The computer goes to sleep
* The computer goes offline
* The application crashes

### Inactivity Threshold

During the reclamation process, the server compares the **Last Accessed Date** with the current date  to decide whether a license is deemed inactive.

You can configure the inactivity window using the **Inactivity Threshold** setting:

* Navigate to:\
  **QLM Management Console → Manage Keys → Options → Cloud Licenses**

This setting defines how long a license can remain inactive before being reclaimed.

### Offline Licenses

If a license was checked-out for offline usage, the reclamation process honors the offline expiry date. If the offline expiry date has been reached, the license will be reclaimed.

### Reclamation Process

The reclamation can be triggered automatically via the QLM Agent service or manually.

When enabled, the QLM Agent Service  contacts the server at regular intervals and performs the reclamation process. 

To manually trigger the reclamation process, go to **QLM Management Console → Manage Keys → Options → Cloud Licenses** and click 'Reclaim inactive licenses now".

### Configuration

To enable automatic license reclamation:

* Launch the QLM Management Console
* Go to the Manage Keys tab and select Options
* Go to the Cloud Licenses tab
* Select your License Server
* Set the Inactivity threshold in minutes

> **Note:** For Soraco-hosted license servers, the minimum allowed value is 3 **½ hours (210 minutes)**.

* Set the Reclamation timer frequency in minutes

> **Note:** For Soraco-hosted license servers, the minimum allowed value is **6 hours (360 minutes)**.

* Select "Enable the QLM Agent to automatically reclaim licenses"

Note that the [QLM Agent Service ](/docs/qlm-agent/qlm-agent-service.md)must be running on your workstation.

### Important Note

If you have upgraded from a previous version of QLM, you should wait 24 hours following the upgrade before enabling license reclamation. If you do not, licenses that are still active will be reclaimed.


---

# 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.soraco.co/docs/floating-licenses/cloud-floating-licenses/cloud-license-reclamation.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.