I am trying to implement Bulk Operations in Magento 2.3.1 using the docs here as a reference.

When I call scheduleBulk on the BulkManagementInterface the operation is saved and can be viewed from the Bulk Action log but I get the following exception and my consumer never processes the operation:

Message queue topic "example.topic" is not configured.

I have the following files in app/etc:


<?xml version="1.0"?>
<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:magento:framework:ObjectManager/etc/config.xsd">
    <type name="Magento\Framework\MessageQueue\MergerFactory">
            <argument name="mergers" xsi:type="array">
                <item name="ExampleConsumer" xsi:type="string">Vendor\Module\Model\Merger</item>


<?xml version="1.0"?>
<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:magento:framework:Communication/etc/communication.xsd">
    <topic name="example.topic" request="Magento\AsynchronousOperations\Api\Data\OperationInterface">
        <handler name="processExampleOperation" type="Vendor\Module\Model\Consumer" method="processOperation"/>


<?xml version="1.0"?>
<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:magento:framework-message-queue:etc/consumer.xsd">
    <consumer name="ExampleConsumer" queue="example_queue" connection="db" handler="Vendor\Module\Model\Consumer::processOperation"/>


<?xml version="1.0"?>
<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:magento:framework-message-queue:etc/publisher.xsd">
    <publisher topic="example.topic">
        <connection name="db" exchange="example.exchange" />


<?xml version="1.0"?>
<config xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="urn:magento:framework-message-queue:etc/topology.xsd">
    <exchange name="example.exchange type="topic" connection="db">
        <binding id="ExampleBinding" topic="example.topic" destinationType="queue" destination="example_queue"/>

Here is a snippet where I call scheduleBulk:

$bulkUuid = $this->_identityService->generateId();
$bulkDescription = 'Example Bulk Operation';
$operations = [];
$serializedData = [
    'entity_id' => $id,
    'entity_link' => $this->_urlBuilder->getUrl('vendor/controller/' . $id),
    'meta_information' => 'Meta Information',
$data = [
    'data' => [
        'bulk_uuid' => $bulkUuid,
        'topic_name' => 'example.topic',
        'serialized_data' => $this->_jsonHelper->jsonEncode($serializedData),
        'status' => OperationInterface::STATUS_TYPE_OPEN,

$operation = $this->_operationFactory->create($data);
$operations[] = $operation;

$userId = $this->_userContext->getUserId();
$result = $this->_bulkManagement->scheduleBulk($bulkUuid, $operations, $bulkDescription, $userId);

if (!$result) {
    throw new \Magento\Framework\Exception\LocalizedException(
        __('Something went wrong while processing the request.')

When I run bin/magento queue:consumers:list my consumer is listed, and when I run start it is started.

The exception is thrown from

Magento\Framework\MessageQueue\Config in the getPublisherConfigByTopic function on line 184

. If I log $this->queueConfigData->get() at the top of that function it is an empty array.

Is there an issue with my configuration above that would be preventing it from being loaded?

Note: I have modified the sample code above and replaced with example data.

  • I have a same problem. But when add a message in the queue the exception is throw. Aug 15, 2019 at 0:45

1 Answer 1


The Example you mentioned (https://devdocs.magento.com/guides/v2.3/extension-dev-guide/message-queues/implement-bulk.html) seams to be fore ampq only. I'am guessing you are trying to use the DB-Backend. In that case you need to create "queue.xml" as well and run setup:upgrade again. Example here: https://devdocs.magento.com/guides/v2.3/extension-dev-guide/message-queues/config-mq.html - be ware that the XSD-Path is wrong! For an working example have a look at the implementation in "module-catalog"

  • I had a similar issue and thought that setup:di:compile was all I needed. The setup:upgrade is what got mine working. THanks! Oct 21, 2020 at 1:52

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.