New bulk schedule doesn't create operations automatically

[duckchip]

Preconditions (*)

1. Magento 2.3.1

Steps to reproduce (*)

1. Create a new bulk schedule

$bulkDescription = $this->getBulkMessage($order);
$bulkUuid = $this->identityService->generateId();

$data = ['just' => 'some dummy'];
$operationData = [
    'data' => [
        'bulk_uuid' => $bulkUuid,
        'topic_name' => self::TOPIC_NAME,
        'serialized_data' => $this->serializer->serialize($data),
        'status' => \Magento\Framework\Bulk\OperationInterface::STATUS_TYPE_OPEN,
    ]
];

$operation = $this->operationsFactory->create($operationData);

$this->bulkManagement->scheduleBulk(
    $bulkUuid,
    [$operation],
    $bulkDescription,
    $this->userContext->getUserId()
);

In this scenario we add 1 operation to a bulk. The moment scheduleBulk is called, a new record inside the magento_bulk table is created.

Even with the queues up and running the operations are not created and stay "Pending"

I think the problem relies in the fact that the operation entities are never saved to the database.

Following function of class Magento\AsynchronousOperations\Model\BulkManagement

/**
     * Publish list of operations to the corresponding message queues.
     *
     * @param array $operations
     * @return void
     */
    private function publishOperations(array $operations)
    {
        $operationsByTopics = [];
        foreach ($operations as $operation) {
+            $this->entityManager->save($operation);
            $operationsByTopics[$operation->getTopicName()][] = $operation;
        }
        foreach ($operationsByTopics as $topicName => $operations) {
            $this->publisher->publish($topicName, $operations);
        }
    }

Adding this line $this->entityManager->save($operation); in the publicOperations function, resolves that problem for me.

Expected result (*)

1. [Screenshots, logs or description]
2. When a bulk is scheduled, the operations are created automatically

Actual result (*)

1. [Screenshots, logs or description]
2. When a bulk is scheduled, the operations are not created

[m2-assistant]

Hi @duckchip. Thank you for your report.
To help us process this issue please make sure that you provided the following information:

• Summary of the issue
• Information on your environment
• Steps to reproduce
• Expected and actual results

Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:

@magento give me 2.3-develop instance - upcoming 2.3.x release

For more details, please, review the Magento Contributor Assistant documentation.

@duckchip do you confirm that you were able to reproduce the issue on vanilla Magento instance following steps to reproduce?

• yes
• no

---

• Join Magento Community Engineering Slack and ask your questions in #github channel.

[vijay-wagento]

@magento give me 2.3-develop instance - upcoming 2.3.x release

[magento-engcom-team]

Hi @vijay-wagento. Thank you for your request. I'm working on Magento 2.3-develop instance for you

[magento-engcom-team]

Hi @vijay-wagento, here is your Magento instance.
Admin access: https://i-23958-2-3-develop.instances.magento-community.engineering/admin
Login: admin Password: 123123q
Instance will be terminated in up to 3 hours.

[duckchip]

I will close this issue since there's a workaround (thanks to @nuzil for sending me in the right direction). This should be documented in the devdocs as well (will create a PR for that later.)

The trick for saving those operations is by calling the Operations Repository.

Given the example of the devdocs

public function execute($operationData)
    {
        $operationCount = count($operationData);
        if ($operationCount > 0) {
            $bulkUuid = $this->identityService->generateId();
            $bulkDescription = 'Specify here your bulk description';

            $operations = [];
            foreach ($operationData as $operation) {

                $serializedData = [
                    //this data will be displayed in Failed item grid in ID column
                    'entity_id' => $operation['entity_id'],
                    //add here logic to add url for your entity(this link will be displayed in the Failed item grid)
                    'entity_link' => $this->urlBuilder->getUrl('your_url'),
                    //this data will be displayed in Failed item grid in the column "Meta Info"
                    'meta_information' => 'Specify here meta information for your entity',//this data will be displayed in Failed item grid in the column "Meta Info"
                ];
                $data = [
                    'data' => [
                        'bulk_uuid' => $bulkUuid,
                        //topic name must be equal to data specified in the queue configuration files
                        'topic_name' => '%your_topic name%',
                        'serialized_data' => $this->jsonHelper->jsonEncode($serializedData),
                        'status' => OperationInterface::STATUS_TYPE_OPEN,
                    ]
                ];

                /** @var OperationInterface $operation */
                $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.')
                );
            }
        }

We'll have to call use the MassSchedule:

$this->massSchedule->publishMass( 'async.V1.inventory.bulk-product-source-transfer.POST', $operations, null, $userId );

instead of

$this->bulkManagement->scheduleBulk($bulkUuid, $operations, $bulkDescription, $userId);

since the MassSchedule uses the OperationRepository to save the Operation entities.

[martinog22]

Hello,
i have still the problem in magento 2.3.2
I tried it with the solutions here but no chance.
Is there maybe another solution or a step by step documentation to check it again?
thanks!

[zw1111]

Hello,
i have still the problem in magento 2.3.2
I tried it with the solutions here but no chance.
Is there maybe another solution or a step by step documentation to check it again?
thanks!

I am also having this issue with Magento 2.3.2. The message still states "Task "Update attributes for 4 selected products": 1 item(s) have been scheduled for update." even after trying to make the code modifications. It seems that the change does not take into account updates that are already queued. How do you get rid of or cancel a queued update?

[arion-p]

This issue has been closed but the problem remains: Magento bulk actions (the ones offered by magento not custom ones) simply don't work. Yet there is no other open issue to track this.
So will this ever be fixed or is it considered expected behaviour?

[hostep]

@arion-p: if there is no issue tracking your problem, I would suggest you open one 😉
This issue here is indeed something different and not related.

@zw1111: your issue also doesn't sound related, you might find more help here: #23450 (comment)

[arion-p]

@hostep: there was an issue tracking my problem: this one but it was closed. I may be missing something here but here are the facts:

• @duckchip posted this https://magento.stackexchange.com/a/283837/39637 in response to this thread in magento stackexchange: https://magento.stackexchange.com/questions/281723/magento-2-bulk-actions-not-starting
• Then he created this ticket and the related PR.
• The PR was abandoned and a different fix was suggested
• Then this ticket was closed without any other ticket tracking the issue and without any fix (either the original or the second one) being applied.

The end result is that the issue described in the 1st post is not going to be fixed because there is no longer an open ticket about it.

btw @zw1111's issue is also exactly the same as the one described in the 1st post (and in the stack exchange thread mentioned above as well as the this thread in magento community: https://community.magento.com/t5/Magento-2-x-Admin-Configuration/Bulk-Actions-issue/td-p/138226)

[hostep]

@arion-p: I can't reproduce the issue from stackexchange or the community forums on a vanilla 2.3.2 installation with a working cronjob and working message queue consumers.

This issue here is for custom written bulk actions, not for the ones included in Magento by default.

So what I suspect is that something is preventing the message queue consumers to spawn somehow, can you read #23450 (comment) and do some debugging and try to figure out why they aren't spawning in your case?

Helping in finding the cause might get us closer to figuring out how to solve it for everybody, thanks! 🙂