Two things update separately: the program, and the modules. Both from Settings → Info, and neither by itself.
The program
Check for updates… asks whether there is a newer version.
If there is, you get the version number and what is new, with a link to read more. Choosing to download fetches and checks it; when it is ready, the program has to close before it can be installed, and it asks first.
Nothing happens without you. No background downloads, no prompts during a service, no restart you did not choose.
The modules
Check for module updates… does the same for the modules that belong to your account. You get a list: which module, from which version to which, and which are new.
Fetching them stops the modules for a moment. The base program keeps running — the cue list, the outputs, the broadcast — but anything a module provides is briefly gone.
When to do it
After a service, never before one. That is the whole advice.
An update half an hour before a broadcast is the update you install on Monday. The program will not push you; the only pressure is your own.
Two more habits worth having on a machine that matters:
Update one machine first where there are several, and run a real rundown on it before doing the rest.
Write down which version you were on. Settings → Info tells you now; it does not tell you what you had last month.
What an update touches
| Updated | Left alone |
|---|---|
| The program | Your rundowns, songs and exports |
| The engine, when the new version needs another one | Your settings, scenes and designs |
| The modules, separately | Your media |
The configuration folder survives an engine replacement deliberately — see the installation in detail.
Why the update check is built in at all
Everything else that talks to a service is a module’s job. This is the deliberate exception: it is about the program itself, and putting it in a module would mean it disappears the moment somebody switches that module off — leaving exactly the installation that is behind with no way to find out.