PHPackages                             magentix/magento-module-message-queue - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Queues &amp; Workers](/categories/queues)
4. /
5. magentix/magento-module-message-queue

ActiveMagento2-module[Queues &amp; Workers](/categories/queues)

magentix/magento-module-message-queue
=====================================

100.1.1(5mo ago)121PHPPHP ^8.2

Since Dec 3Pushed 5mo ago1 watchersCompare

[ Source](https://github.com/magentix/magento-module-message-queue)[ Packagist](https://packagist.org/packages/magentix/magento-module-message-queue)[ RSS](/packages/magentix-magento-module-message-queue/feed)WikiDiscussions main Synced 1mo ago

READMEChangelog (2)Dependencies (2)Versions (3)Used By (0)

Magentix Message Queue Module
=============================

[](#magentix-message-queue-module)

A Magento 2 module that allows you to manually execute MySQL message queue (MysqlMq) messages by their identifier or topic.

Installation
------------

[](#installation)

```
composer require magentix/magento-module-message-queue
```

Description
-----------

[](#description)

This module adds a CLI command `queue:message:process` that allows you to execute one or more queue messages without having to run the full consumer. This is particularly useful for:

- Executing the handler associated with a topic without running the entire queue
- Debugging a specific message that is causing issues
- Replaying an already processed message (using the **--force** option)

**Important:** This module only works with the MySQL (MysqlMq) backend. It is not compatible with RabbitMQ.

The `queue:message:status` command displays the status of messages in MysqlMq.

Scenarios
---------

[](#scenarios)

Display **sales\_rule.codegenerator** topic statuses:

```
bin/magento queue:message:process --topic=sales_rule.codegenerator
+----+--------------------------+-----------+---------------------+
| ID | Topic                    | Status    | Update On           |
+----+--------------------------+-----------+---------------------+
| 4  | sales_rule.codegenerator | New       | 2025-12-01 18:23:52 |
| 5  | sales_rule.codegenerator | New       | 2025-12-02 22:10:54 |
| 9  | sales_rule.codegenerator | New       | 2025-12-03 16:05:28 |
+----+--------------------------+-----------+---------------------+
```

Running all new **sales\_rule.codegenerator** topics:

```
bin/magento queue:message:process --topic=sales_rule.codegenerator
Message 4: Magento\SalesRule\Model\Coupon\Consumer::process
Message 5: Magento\SalesRule\Model\Coupon\Consumer::process
Message 9: Magento\SalesRule\Model\Coupon\Consumer::process
```

Running a specific topic already executed, nothing happens:

```
bin/magento queue:message:process --id=4
```

Running a specific topic already executed using the **--force** option:

```
bin/magento queue:message:process --id=4 --force=1
Message 4: Magento\SalesRule\Model\Coupon\Consumer::process
```

Usage
-----

[](#usage)

### Syntax

[](#syntax)

```
bin/magento queue:message:status [options]
```

```
bin/magento queue:message:process [options]
```

### Options

[](#options)

OptionShortcutDescription`--id``-m`Message ID in the `queue_message` table`--topic``-t`Topic name (e.g., `product_alert`, `sales.rule.quote.trigger.recollect`)`--area``-a`Area code (`global`, `adminhtml`, `frontend`)`--force``-f`Force execution even if the message status is not NEW### Examples

[](#examples)

#### Display all messages

[](#display-all-messages)

```
bin/magento queue:message:status
```

#### Filter by topic

[](#filter-by-topic)

```
bin/magento queue:message:status --topic=product_alert
```

#### Display a specific message

[](#display-a-specific-message)

```
bin/magento queue:message:status --id=123
```

#### Execute a specific message by its ID

[](#execute-a-specific-message-by-its-id)

```
bin/magento queue:message:process --id=123
```

#### Execute all messages for a topic

[](#execute-all-messages-for-a-topic)

```
bin/magento queue:message:process --topic=product_alert
```

#### Execute a specific message for a topic

[](#execute-a-specific-message-for-a-topic)

```
bin/magento queue:message:process --id=456 --topic=product_alert
```

#### Force execution of an already completed or processed message

[](#force-execution-of-an-already-completed-or-processed-message)

```
bin/magento queue:message:process --id=789 --force=1
```

Technical Notes
---------------

[](#technical-notes)

### Multiple Handlers

[](#multiple-handlers)

If a topic has multiple handlers configured in `communication.xml`, **all handlers will be executed** for each message.

### Error Handling

[](#error-handling)

If an error occurs during message decoding, an error message is displayed and processing moves to the next message. The message status is not modified in case of error.

###  Health Score

35

—

LowBetter than 80% of packages

Maintenance72

Regular maintenance activity

Popularity5

Limited adoption so far

Community8

Small or concentrated contributor base

Maturity48

Maturing project, gaining track record

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

###  Release Activity

Cadence

Every ~0 days

Total

2

Last Release

157d ago

### Community

Maintainers

![](https://www.gravatar.com/avatar/884247993aa6a48e2c3a2071a98e0bc2c92e3519ecc8d5b22a9b07e5183a5a0f?d=identicon)[magentix](/maintainers/magentix)

---

Top Contributors

[![magentix](https://avatars.githubusercontent.com/u/346889?v=4)](https://github.com/magentix "magentix (3 commits)")

### Embed Badge

![Health badge](/badges/magentix-magento-module-message-queue/health.svg)

```
[![Health](https://phpackages.com/badges/magentix-magento-module-message-queue/health.svg)](https://phpackages.com/packages/magentix-magento-module-message-queue)
```

###  Alternatives

[league/geotools

Geo-related tools PHP 7.3+ library

1.4k5.3M26](/packages/league-geotools)[amphp/parser

A generator parser to make streaming parsers simple.

14952.8M16](/packages/amphp-parser)[react/async

Async utilities and fibers for ReactPHP

2238.8M170](/packages/react-async)[dotdigital/dotdigital-magento2-extension

Dotdigital for Magento 2

50374.2k18](/packages/dotdigital-dotdigital-magento2-extension)[run-as-root/magento2-message-queue-retry

Provides message queue retry processing functionality via RabbitMQ's dead letter exchange.

64102.8k](/packages/run-as-root-magento2-message-queue-retry)[belvg/module-sqs

N/A

1544.4k](/packages/belvg-module-sqs)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)
