The Change Logs page is your running history of what’s new in Synconix: bug fixes, improvements, and brand-new features. It also shows the latest version available in each tier (STABLE, RELEASE, BETA) so you can decide when to update.

How it’s organized

• Entries are grouped by version family (e.g., 1.6.x, 1.5.x).
• Each line is tagged with a badge: BUG-FIX issue resolved, UPDATE enhancements & polish, FEATURE new capability.
• The counters at the top show the newest builds per tier: STABLE (safest for production), RELEASE (release-candidate quality), and BETA (latest, still maturing).

When should I upgrade?

• Production: stay on STABLE unless you specifically need something newer.
• Pre-prod / lab: use RELEASE or BETA to validate upcoming changes.
• If a fix or feature listed here matters to you, switch your tier on the Version page and apply the update.

Where to change the tier

Go to Version (admin only) and select STABLE, RELEASE, or BETA. The panel will pull updates from the matching channel. If you enabled Auto Updates in Settings → General, new builds in that tier will install automatically.

Reading entries (quick examples)

• FEATURE Monitor page — A brand-new live view for running schedules and logs.
• UPDATE Rsync 3.4.1 — All nodes will be upgraded to the newer rsync engine.
• BUG-FIX Old points deletion — Corrects cases where aged backup points were not removed.

Good to know

• Updates are designed to be rolling: running backups continue; new jobs pick up the new components.
• Some changes (e.g., new rsync binaries) are applied on the storage/production nodes the next time those nodes are contacted by the panel installer routines.
• You can track what changed on your system in Users Activity and Backup Logs.

Troubleshooting after an update

• “I don’t see the new feature.” Check that your Version tier matches the feature’s section in the changelog (e.g., it may be in 1.6.x but you’re on 1.5.x).
• “Limit/plan change doesn’t apply.” Open License and click Force license update to resync.
• “Rsync reports an older version.” Re-check node connectivity; the helper will push the new rsync on the next maintenance run.

Best practice

Validate major changes (e.g., new transfer modes or compression) on a non-production schedule first. Keep your tier on STABLE for production unless a listed fix/feature justifies an earlier adoption.