fix: wait the full hour and keep Hold for automatic owed-plugin retries on a schedule (#201355) * fix(update): keep the owed-plugin retry cooldown and hold on cron schedules With update.auto.schedule set, the owed-plugin retry measured its one-hour cooldown against the current cron window, so a five-minute schedule could restart the Gateway minutes after the automatic update that installed the version. A later check outside the window also retired an announced retry, so a held retry never resumed. The retry now gates new campaigns on elapsed time since that attempt, and a check that still finds the row owed keeps an announced campaign, including its hold. The ledger still bounds each owed row to one retry per version. * test(update): keep owed-plugin retries inside cron windows after the cooldown * test(update): prove the owed-plugin retry cooldown through a scheduled managed Gateway * test(update): report the schedule cell's phases and compare retry versions * test(update): drop the unfinished schedule Docker cell
Current
·
C2
·2026-11
fix: wait the full hour and keep Hold for automatic owed-plugin retri…
Find Your Interest
- fix: let automatic updates finish plugin updates that an earlier upda…
- fix: show the plugin-update restart countdown next to the update that…
- fix(update): keep updating when a pre-migration database image does n…
- fix: keep a doubtful killed-update recovery on the repair path (#201361)
- fix: let updates finish when plugins change no config and openclaw.js…
- fix(update): snapshot busy WAL databases instead of refusing admissio…
- fix: finish updates when another tool reads OpenClaw's databases duri…
- fix: Git checkout updates across a schema change no longer end as pos…
- fix: let package updates start while the Gateway is writing to an age…
- fix: show the Access page when you turn on OpenClaw ID with a plugin …
Current
·
C2
·2026-11






