Maintenance & Watchdog
Guides and release notes are shown in their original language.
On this page
← All guides · MANAGE & MAINTAIN
Synix coordinates supported backups, updates, restarts, and process recovery. Automation still needs a running PC, available storage, and a server configuration that has been tested.
Backup on Start and Update on Start
Configure these per server under Automation.
- Backup on Start creates a stopped-server backup before applicable launches.
- Update on Start runs the supported game update check before launch.
- Crash-recovery starts deliberately skip the normal backup routine.
A requested backup must succeed before update or launch continues. A requested update must also succeed before launch. A failure leaves the server stopped and identifies the step needing attention; the same rule applies to scheduled maintenance. An unavailable custom backup folder is not silently replaced with a default.
A Synix application update is separate from an individual game's update. SteamCMD validation can redownload managed game files; back up modifications first instead of assuming every customized file will remain untouched.
See Backups, Restore & Transfers for coverage and retention.
Scheduled Smart Maintenance
- Open the selected server's automation/schedule settings.
- Enable its schedule and choose the days and time.
- Enable Smart Maintenance and select the available backup/update options.
- Decide whether to wait for players and set the maximum delay.
- Save, then test the workflow during an attended maintenance window.
The schedule uses the PC's local time. Keep the clock and time zone correct.
When due, Synix can defer while players are connected, then coordinate stopping the verified process group, backing up while stopped, updating, and restarting according to the selected options.
The maximum delay is a limit, not a promise to wait forever. Maintenance can proceed when it expires even if players remain. A zero delay does not provide a waiting period.
Player-aware scheduling is only as useful as the game's available player information. For an API-linked Satisfactory server, stale/unavailable API counts are treated conservatively during the configured waiting period; that does not make every unsupported game's player count reliable.
Review activity messages and notify players before scheduled work.
Watchdog recovery
The watchdog monitors tracked server processes and can initiate configured recovery after an unexpected exit or detected problem.
Use Stop or Restart in Synix for intentional lifecycle actions. Killing a server in Task Manager or stopping it through an unrelated tool can look like a crash and trigger recovery.
Recovery checks and timing vary with server state and launch behavior. Do not assume one fixed timeout covers every game, or that a query failure proves the game process crashed.
If a server repeatedly restarts, stop it through Synix, inspect the latest game log, and fix the underlying configuration/runtime/mod problem before trying again.
Resource checks
Synix checks resource pressure before certain launches to reduce the risk of overloading the host. These checks do not allocate a hard CPU/RAM container or guarantee that Windows cannot run out of resources later.
Leave enough memory and disk space for Windows, the game, updates, and backups. A configured Minecraft memory limit is a game/runtime setting, not a universal limit for all server processes.
Reopening Synix and background operation
Synix can recover ownership of recognized running processes when reopened. Do not start a second copy of a server just because the dashboard is still checking existing processes.
Optional background-agent settings support monitoring at Windows sign-in. Do not confuse closing a child window, minimizing the main window, and explicitly exiting the application. Review the configured behavior and any exit prompt.
Scheduled work requires the relevant Synix process/agent and Windows session to be available. A sleeping, shut-down, or offline PC cannot perform normal scheduled downloads or restarts.
External deployments
Some games own virtual machines or other deployment services. In particular, Dune's launcher process does not reliably represent the running battlegroup. See Dune: Awakening Server Guide instead of applying ordinary process-watchdog assumptions.
For incomplete operations and restore retry behavior, see Workflow Safety & Recovery.
For notifications, see Discord Notifications.