Drupal is a registered trademark of Dries Buytaert
drupal 11.3.7 Update released for Drupal core (11.3.7)! drupal 11.2.11 Update released for Drupal core (11.2.11)! drupal 10.6.7 Update released for Drupal core (10.6.7)! drupal 10.5.9 Update released for Drupal core (10.5.9)! cms 2.1.1 Update released for Drupal core (2.1.1)! 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). eca 3.1.1 Minor update available for module eca (3.1.1). layout_paragraphs 2.1.3 Minor update available for module layout_paragraphs (2.1.3). ai 1.3.3 Minor update available for module ai (1.3.3). ai 1.2.14 Minor update available for module ai (1.2.14). node_revision_delete 2.0.3 Minor update available for module node_revision_delete (2.0.3). moderated_content_bulk_publish 2.0.52 Minor update available for module moderated_content_bulk_publish (2.0.52). klaro 3.0.10 Minor update available for module klaro (3.0.10). klaro 3.0.9 Minor update available for module klaro (3.0.9). layout_paragraphs 2.1.2 Minor update available for module layout_paragraphs (2.1.2). geofield_map 11.1.8 Minor update available for module geofield_map (11.1.8).

batch_messenger

3 sites Security covered
View on drupal.org

Batch Messenger is divided into three pieces of functionality:

  • Group Symfony Messenger messages together into a collection. (Base functionality)
  • Expose a UI of progress of each collection. (Optional, enabled by default)
  • Intercept Drupal Batch API calls (batch_set()) and replace with Messenger internals. (Optional, enabled by default)

This allows you to adopt Symfony Messenger, while providing a nice UI for the user. Performance of operations improve dramatically, as they may be worked in parallel, instead of single threaded. Message resources (CPU/memory, etc) can be increased in a worker, while granting the possibility to reduce web thread resources since they don't need to scale up for Batch API operations.

When the legacy Batch API is used (\batch_set), the UI is retained, and we provide status updates to the user despite operations not actually running in the web requests.

The module is a drop-in replacement for Batch API. If you encounter issues, uninstalling the module will return existing behavior. Though, any in-progress batches will be deleted.

More information can be found in the README.

Activity

Total releases
6
First release
Jul 2025
Latest release
7 months ago
Release cadence
11 days
Stability
83% stable

Release Timeline

Releases

Version Type Release date
1.0.2 Stable Sep 9, 2025
1.0.1 Stable Sep 5, 2025
1.1.1 Stable Sep 5, 2025
1.1.0 Stable Jul 15, 2025
1.x-dev Dev Jul 15, 2025
1.0.0 Stable Jul 15, 2025