From c51951d6a87019b9577505a828bea3914bbb58e7 Mon Sep 17 00:00:00 2001
From: Lakshya77089 <lakshyasharma7708@gmail.com>
Date: Fri, 19 Jun 2026 14:14:03 +0530
Subject: [PATCH] fix: restore auto-update registration broken by interval
 refactor

The "improve updater registration" refactor introduced two regressions in
the service mixin that disable auto-update for every service:

- initAutoUpdate() returned early when `interval > 0` and only called
  register() when the interval was 0, i.e. the guard was inverted: a valid
  interval skipped registration, and a disabled one registered with 0.
- getUpdateInterval() now resolves the interval into a local `interval`
  variable (supporting `updateIntervalMs` and the deprecated keys), but the
  service-specific branch still parsed `this.item.updateInterval`. Setting
  `updateIntervalMs` left that key undefined, so it returned 0 (disabled).

Register when `interval > 0`, and parse the resolved `interval` value.
---
 src/mixins/service.js | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/src/mixins/service.js b/src/mixins/service.js
index 8248c7e..a26c6bb 100644
--- a/src/mixins/service.js
+++ b/src/mixins/service.js
@@ -90,7 +90,7 @@ export default {
       }
 
       const interval = this.getUpdateInterval();
-      if (interval > 0) {
+      if (interval <= 0) {
         return;
       }
       updateScheduler.register(this, interval, this.autoUpdateMethod);
@@ -128,7 +128,7 @@ export default {
 
       // Use service-specific interval if defined
       if (interval) {
-        return parseInt(this.item.updateInterval, 10) || 0;
+        return parseInt(interval, 10) || 0;
       }
 
       // Use global auto-update configuration