> For the complete documentation index, see [llms.txt](https://docs.devolutions.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devolutions.net/unigetui/guides/updates/schedule.md).

# Run updates on a schedule

Choose when UniGetUI checks for updates and when it installs them, so updates happen at a time that suits you.

Checking for updates and installing them are two separate tasks. That lets you, for example, check every hour but only install on Friday at noon, when an app closing for an update won't interrupt you.

Out of the box, UniGetUI checks for updates every hour and installs nothing by itself.

{% hint style="warning" %}
Scheduled tasks only run while UniGetUI is running. Leaving it minimized in the notification area is enough. See [Keep UniGetUI running](#keep-unigetui-running) below.
{% endhint %}

{% stepper %}
{% step %}

### Open the schedule

Go to ***Settings*** – ***Scheduled maintenance***.

Each task has a toggle. Turn it on to see its options.
{% endstep %}

{% step %}

### Choose when to check for updates

1. Make sure ***Check for package updates*** is turned on.
2. In ***Repeat***, choose ***On a fixed interval***, ***Every day*** or ***On selected days***.
3. Set ***Check every***, or the ***Days*** and ***Start time***, depending on your choice.
   {% endstep %}

{% step %}

### Choose when to install updates

1. Turn on ***Install available updates***.
2. In ***Repeat***, choose:
   * ***After every update check*** to install as soon as updates are found (the default), or
   * ***Every day*** or ***On selected days***, with a ***Start time***, to install at a set moment.
3. In ***Install***, choose ***All available updates*** or ***Only packages marked for automatic updates***. See [Choose which apps update automatically](/unigetui/guides/updates/automatic-updates.md).
   {% endstep %}

{% step %}

### Decide what happens if the computer was off

In ***If the scheduled time is missed***, choose:

* ***Run whenever UniGetUI next starts*** to catch up as soon as possible,
* ***Run within*** a delay, to catch up only if the miss was recent, or
* ***Skip until the next occurrence*** to wait for the next scheduled time.

For laptops that are often off at the scheduled time, ***Run whenever UniGetUI next starts*** is usually the best choice.
{% endstep %}

{% step %}

### Test it

Click ***Run now*** next to a task. The last and next run times appear beside the button, with the error if the last run failed.
{% endstep %}
{% endstepper %}

## Keep UniGetUI running

1. Go to ***Settings*** – ***User interface preferences***.
2. Turn on ***Close UniGetUI to the system tray***. Closing the window then keeps UniGetUI running in the notification area.
3. On Windows, click ***Open*** next to ***Manage UniGetUI autostart behaviour*** and make sure UniGetUI starts when you sign in.

## Good to know

* The same page also schedules ***Local package backup*** and ***Cloud package backup***. See [Back up your app list automatically](/unigetui/guides/new-computer/backup.md).
* Installed updates follow your safety settings, like the minimum age and the battery and metered connection rules. See [Avoid brand-new releases](/unigetui/guides/updates/update-safely.md).
* Tasks don't run? See [Scheduled updates don't run](/unigetui/help/troubleshooting/scheduled-updates-dont-run.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 by asking a question.

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

```
GET https://docs.devolutions.net/unigetui/guides/updates/schedule.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.