Drupal is a registered trademark of Dries Buytaert
cms 2.1.3 — Update released for Drupal core (2.1.3)! drupal 10.5.11 — Update released for Drupal core (10.5.11)! drupal 11.3.11 — Update released for Drupal core (11.3.11)! drupal 11.2.13 — Update released for Drupal core (11.2.13)! drupal 10.6.10 — Update released for Drupal core (10.6.10)! cms 2.1.2 — Update released for Drupal core (2.1.2)! drupal 11.1.10 — Update released for Drupal core (11.1.10)! drupal 10.5.10 — Update released for Drupal core (10.5.10)! drupal 10.4.10 — Update released for Drupal core (10.4.10)! drupal 11.2.12 — Update released for Drupal core (11.2.12)! drupal 11.3.10 — Update released for Drupal core (11.3.10)! drupal 10.6.9 — Update released for Drupal core (10.6.9)! drupal 10.6.8 — Update released for Drupal core (10.6.8)! drupal 11.3.9 — Update released for Drupal core (11.3.9)! drupal 11.3.8 — Update released for Drupal core (11.3.8)! 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)!
← All modules

batch_messenger

4 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).
    Simply add a CollectionItem stamp with a shared ID.
  • 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
7
First release
Jul 2025
Latest release
6 days ago
Release cadence
53 days
Stability
86% stable

Release Timeline

Releases

Version Type Release date
1.1.2 Stable May 27, 2026
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