Fix Clash Verge Rev backups after restart

In official issue #8331, a user on Windows 11 with Clash Verge Rev v2.5.8 configured backups every 1 hour. After fully quitting and reopening the app, they left the settings unchanged and the device awake for more than 1 hour, yet saw neither an automatic archive nor a corresponding Backup log entry.

After that user changed a setting and waited another full interval, a scheduled backup appeared. This comparison helps identify the problem; changing an arbitrary setting after every launch is not a lasting fix. You do not need to keep changing the language, proxy or subscription to investigate it.

This guide draws on that Windows report, the shared backup code and the official fix notes. It does not claim that every platform or older version was tested and found affected. The issue is officially fixed in v2.5.9. First rule out normal timing conditions, such as an incomplete interval or an app that has already exited.

Protect the current configuration before waiting for another scheduled backup. Open Settings → Verge Advanced Setting → Backup Setting. Under Local backup, click Backup, then open View history and export the new ZIP outside the app's data directory.

Check that the exported file exists and opens, then inspect profiles.yaml, profiles/ and your essential configuration. A ZIP is an archive, not encryption. It may contain subscription tokens, node passwords and local overrides, so keep it in protected storage that you control.

If a manual backup also fails, save the first error and make a separate copy of the existing data before investigating the file-write failure. Do not immediately attribute it to the schedule-after-restart defect, or experiment by emptying the app directory, restoring an old ZIP or uninstalling the app.

Official PR #8386 explains that the old implementation sent the saved backup settings before the timer task subscribed. With no receiver, send on the watch channel did not retain the new value. The task that started later therefore read the default disabled state and waited for another settings change.

The fix replaces both the startup and settings-refresh sends with send_replace, so a task that starts later can read the saved value. It was merged and included in the stable v2.5.9 release published on 11/2/2026. An issue being closed or a development-branch change alone would not establish that a fix had shipped.

This is a backup-scheduling issue in the Clash Verge Rev app. Updating only the Mihomo core, refreshing a subscription or restarting the core cannot replace updating the app. If you already run a later stable release with separate evidence that it includes this fix, there is no need to downgrade to v2.5.9 for this guide.

The app's own timer task creates local backup files. It is neither a separate operating-system backup service nor a calendar task that runs at a particular time each day. Do not expect backups while the app is fully exited, or assume it will catch up on missed backups when reopened.

The stable fix verified for this guide is Clash Verge Rev v2.5.9. Use the official v2.5.9 Release linked in the references and choose your operating system and processor architecture. This maintenance run did not update the installers hosted on this site; an older v2.5.8 mirror is not the fixed package.

If you cannot obtain the official package or installation fails, keep the working environment and the error, then resolve that download or installation problem first. Do not disable signature checks or security protection, or treat an older package being downloadable on a website as a successful update.

Under Backup Setting → Automatic backup, check Enable scheduled backup and Backup frequency. The pinned v2.5.9 code defaults to 24 hours and allows 1–168 hours. You may temporarily choose 1 hour for observation; record the original value, save, then fully quit and reopen the app.

Start timing from this reopening. Keep the app running and the device awake, without changing settings or restarting. Do not edit global overrides or scripts to trigger other backups. Wait longer than a full interval; the absence of a file immediately after launch is not evidence of failure.

Restarting the app or receiving a settings notification starts a fresh full interval. Repeatedly saving settings can keep postponing the observation point. Distinguish this from a schedule that remains enabled but never runs despite a long period with no settings changes.

After the interval, open Local backup → View history, look for a new file and check for Auto backup created (Scheduled) in the logs. A scheduled archive ends in -auto-scheduled.zip. An -auto-merge, -auto-script or manual file alone does not complete this verification.

The pinned code keeps only the latest 20 automatic archives carrying the -auto- marker. Scheduled backups and those triggered by global override or script changes share this limit; it is not 20 for each kind. The local directory is not a permanent history store, so export known-good backups separately.

We have not waited an hour or performed a restore experiment in a real Clash Verge Rev client. These acceptance steps come from the official user report and pinned source code. Passing this site's page, translation and build checks cannot replace checking scheduled backups on your device.

If only the scheduled task fails, continue creating and exporting manual backups. Do not restore over the current configuration merely to test the schedule. If an app rollback or data restore is genuinely needed, fully quit first and keep independent copies from before and after the upgrade. Do not let old and new app versions compete for the only data directory.

The older app may still have this defect: rollback is an emergency measure, not a scheduling fix. After restoring the app and data, check the original Profile, overrides, proxy mode and real connections. Continue saving manual backups externally, and verify the schedule by waiting again as described above.

When reporting to the project, provide the operating system, full app version, original interval, actual launch and settings-save times, manual-backup result, scheduled filename and first redacted error. Do not upload the complete ZIP, subscription link or credentials, or report tests on other platforms that you did not perform as passed.