# Long-running applications

Nuvolos aims to provide the maximal resources for applications that require it, whilst freeing up resources from unused applications to optimize organization resource usage. As described below, we provide convenient default policies that:

* Allow long running computations to finish without user interaction.
* Stop inactive applications, to free up resources for other organization members / minimize credit usage.

We achieve the above through our automatic inactivity stopper as described below.

{% hint style="success" %}
For certain applications such as RStudio, long-running computations are best done using specific features off the app (e.g. RStudio jobs). Please take a look at the [application-specific guides](/user-guides/application-specific-guides.md) as well.
{% endhint %}

## Automatic stopping due to inactivity

In order to efficiently allocate resources, Nuvolos automatically stops inactive applications. Research and Education spaces are handled differently.

### Research Spaces

For **research spaces** Nuvolos considers an application being active if **either**:

* It is actively opened on Nuvolos and in focus in the browser, or
* it is actively computing (using more than half of a single virtual CPU).

In research-purpose spaces, the default inactivity limit is **six hours** for **INCLUDED**-size applications and **one hour** for **CREDIT**-size applications.

For **INCLUDED**-size applications, the inactivity limit can be set between 1 hour and 24 hours by space administrators in the [application configuration menu](/features/applications/configuring-applications.md). This has no effect on **CREDIT**-size applications.

{% hint style="info" %}
Researchers can launch long running computations and their application will keep running until actively computing. If the computation is finished (either due to completion or an error) and the application is not opened on Nuvolos, it will be auto-stopped. We therefore recommend explicitly capturing and saving output logs to ensure that any warnings or errors are captured.
{% endhint %}

### Education spaces

In education-purpose spaces, the default inactivity limit for any application type is **one hour**.

{% hint style="info" %}
To keep an application active in an education space, you need to make sure that the application is in focus in your browser for more than one (uninterrupted) minute every hour.
{% endhint %}

## FAQ

<details>

<summary>My GPU workload was computing but it got stopped - why?</summary>

If your application was not using at least a half of a vCPU during calculation, the automatic stopper will stop the workload. Please post a support request via Intercom and we can help you increase automatic stopper sensitivity.

</details>


---

# Agent Instructions: 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:

```
GET https://docs.nuvolos.com/features/applications/long-running-applications.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.