Drupal is a registered trademark of Dries Buytaert
drupal 11.3.6 — Update released for Drupal core (11.3.6)! drupal 10.6.6 — Update released for Drupal core (10.6.6)! cms 2.1.0 — Update released for Drupal core (2.1.0)! bootstrap 8.x-3.40 — Minor update available for theme bootstrap (8.x-3.40). menu_link_attributes 8.x-1.7 — Minor update available for module menu_link_attributes (8.x-1.7). editoria11y 2.2.22 — Minor update available for module editoria11y (2.2.22). ai 1.2.13 — Minor update available for module ai (1.2.13). ai 1.3.2 — Minor update available for module ai (1.3.2). moderated_content_bulk_publish 2.0.51 — Minor update available for module moderated_content_bulk_publish (2.0.51). moderated_content_bulk_publish 2.0.50 — Minor update available for module moderated_content_bulk_publish (2.0.50). editoria11y 2.2.21 — Minor update available for module editoria11y (2.2.21). eca 3.1.0 — Minor update available for module eca (3.1.0). sophron 3.1.1 — Minor update available for module sophron (3.1.1). ai 1.3.1 — Minor update available for module ai (1.3.1). seven 2.0.0-beta6 — New beta version released for theme seven (2.0.0-beta6). seven 1.0.1-beta1 — First beta version released for theme seven (1.0.1-beta1). ui_patterns 8.x-1.15 — Minor update available for module ui_patterns (8.x-1.15). layout_paragraphs 3.0.0-beta1 — First beta version released for module layout_paragraphs (3.0.0-beta1). raven 7.3.8 — Minor update available for module raven (7.3.8). bamboo_twig 6.0.7 — Minor update available for module bamboo_twig (6.0.7).
← All modules

update_status_kv_flush

No security coverage
View on drupal.org

Fixes a common problem where Drupal's update status page shows "No release history available" after a Redis restart or queue flush. Detects the desync automatically and provides a one-click fix.

Features

Drupal tracks which modules need update checks using two separate stores: a database-backed key-value store and a queue (often Redis-backed). When Redis is flushed or restarted, the queue is wiped but the database entries remain. On the next cron run, Drupal sees all projects already listed in the database and skips re-queuing them — so no update check ever runs, and admin/reports/updates shows "No release history available" for most or all modules.

This module:

  • Detects the desync automatically on the Status report (admin/reports/status)
  • Shows an error-level entry with a one-click fix link when the problem is present
  • Shows an OK status when everything is in sync (no noise when things are healthy)
  • Clears the stale database entries so Drupal can re-queue projects on the next cron run

Use this module if your site uses a Redis queue backend and you have ever seen update status become permanently stuck after a Redis restart or FLUSHALL.

Post-Installation

No configuration is needed. Once enabled, the module runs silently in the background.

If a desync is detected, an error entry titled "Update fetch task store" will appear on admin/reports/status with a "Clear the update fetch task store" link. Click the link, then go to admin/reports/updates and click "Check manually" to trigger an immediate re-fetch. You can also simply wait for the next cron run.

When everything is healthy, the status report shows an OK entry confirming the KV store and queue are in sync.

Additional Requirements

  • Drupal core Update module (enabled by default in most Drupal installations)
  • Drupal 10 or 11

No additional libraries or APIs are required. The module is most useful on sites that use a Redis-backed queue (e.g. via the Redis module), but it works on any Drupal installation.

Recommended modules/libraries

  • Redis — the queue backend most likely to trigger this problem. Using this module alongside Redis gives you automatic detection if a desync occurs.

Activity

Total releases
2
First release
Apr 2026
Latest release
15 hours ago
Release cadence
0 days
Stability
50% stable

Releases

Version Type Release date
1.0.0 Stable Apr 8, 2026
1.0.x-dev Dev Apr 8, 2026