openclaw - 💡(How to fix) Fix UnraidClaw plugin spams 50+ "invalid config" lines during startup despite valid config [1 participants]

Summary

The UnraidClaw plugin spams invalid config: serverUrl: must have required property 'serverUrl', apiKey: must have required property 'apiKey' roughly every 300ms during gateway startup, producing 50+ log lines over ~25 seconds before the gateway reaches ready state. Once ready, the plugin loads correctly and all 40 tools register fine.

The config is valid — serverUrl, apiKey, and tlsSkipVerify are all present under plugins.entries.unraidclaw.config. The issue appears to be a timing problem: plugin config validation runs repeatedly before the config values are fully resolved.

Environment

• OpenClaw: 2026.4.8 (also reproduced on 2026.4.5)
• Install: Docker (ghcr.io/openclaw/openclaw:latest)
• OS: Unraid 6.12.54 / Linux x64
• Plugin: UnraidClaw (bundled)

Config (redacted)

"plugins": {
  "entries": {
    "unraidclaw": {
      "enabled": true,
      "config": {
        "serverUrl": "https://192.168.x.x:9876",
        "apiKey": "REDACTED",
        "tlsSkipVerify": true
      }
    }
  }
}

Observed behavior

Gateway startup log (stderr, timestamps condensed):

17:50:14.827 [gateway] UnraidClaw: registered 40 tools     ← config IS valid
17:50:15.139 [gateway] ready (4 plugins, 1.8s)

17:50:16.861 [plugins] unraidclaw invalid config: serverUrl: must have required property 'serverUrl' ...
17:50:17.160 [plugins] unraidclaw invalid config: ...
17:50:17.472 [plugins] unraidclaw invalid config: ...
  ... (repeats ~50 times, every ~300ms) ...
17:50:41.082 [plugins] unraidclaw invalid config: ...

17:50:41.968 [plugins] UnraidClaw: registered 40 tools     ← registers again, works fine

The plugin validates and registers successfully at 17:50:14, then a separate startup phase hammers the same validation in a tight loop from 17:50:16 to 17:50:41. After that, everything works.

Expected behavior

If the config is valid (which it is — the plugin successfully registers), the validation loop should not fire, or should stop after the first successful registration.

Related issues

• #44398 — Same pattern for channel plugins (health monitor infinite restart of unconfigured WhatsApp plugin, no backoff)
• #61683 — Plugin-scoped config errors should degrade gracefully
• #47654 — Strip unknown keys with warnings instead of crash-looping

This appears to be the tool-plugin variant of the validation-loop family. The config is correct, nested properly under .config, and the plugin works — but some startup phase doesn't see the resolved values and retries aggressively until it does.