async.magento.catalog.api.specialpricestorageinterface.update.post - operations report different result than sent in message

[bjornmeat]

Preconditions (*)

1. Magento Commerce 2.3.4
2. Magento async api endpoint for async.magento.catalog.api.specialpricestorageinterface.update.post

Steps to reproduce (*)

1. Multiple different updates sent for different skus to : /rest/all/async/V1/products/special-price
2. In Magento db operation table and in detailed status for bulk/asynk in API we see the original message.
3. After message is processed. A different sku / message is processed and added to operation table.

Expected result (*)

1. The proper message and result should be saved in Magento operation table.

Actual result (*)

1. Message saved in Magento operation and result from bulk status api endpoint.

{
"operations_list": [
{
"id": 927,
"bulk_uuid": "74bf51dc-60ea-4815-8e7c-047f7a7bdfbb",
"topic_name": "async.magento.catalog.api.specialpricestorageinterface.update.post",
"serialized_data": "{"entity_id":null,"entity_link":"","meta_information":"{\"prices\":[{\"price\":198,\"store_id\":0,\"sku\":\"175025\",\"price_from\":\"2020-04-18 00:00:00\",\"price_to\":\"2020-04-18 23:59:00\"}]}"}",
"result_serialized_data": null,
"status": 4,
"result_message": null,
"error_code": null
}
],
"user_type": 1,
"bulk_id": "74bf51dc-60ea-4815-8e7c-047f7a7bdfbb",
"description": "Topic async.magento.catalog.api.specialpricestorageinterface.update.post",
"start_time": "2020-04-15 09:45:27",
"user_id": 2,
"operation_count": 1
}

2. Result after message processed by queue consumer. (Note bulk id and SKU in result.)
   {
   "operations_list": [
   {
   "id": 927,
   "bulk_uuid": "74bf51dc-60ea-4815-8e7c-047f7a7bdfbb",
   "topic_name": "async.magento.catalog.api.specialpricestorageinterface.update.post",
   "serialized_data": null,
   "result_serialized_data": "[{"message":"Future Update already exists in this time range. Set a different range and try again.","parameters":["138.6","154170","0","2020-04-18 00:00:37","2020-04-18 23:59:38"]},{"message":"The product that was requested doesn't exist. Verify the product and try again. Row ID: SKU = 117890, Store ID: 0, Price From: 2020-04-18 00:00:00, Price To: 2020-04-18 23:59:00.","parameters":["117890","0","2020-04-18 00:00:00","2020-04-18 23:59:00"]},{"message":"The product that was requested doesn't exist. Verify the product and try again. Row ID: SKU = 117890, Store ID: 0, Price From: 2020-04-18 00:00:00, Price To: 2020-04-18 23:59:00.","parameters":["117890","0","2020-04-18 00:00:00","2020-04-18 23:59:00"]},{"message":"The product that was requested doesn't exist. Verify the product and try again. Row ID: SKU = 117890, Store ID: 0, Price From: 2020-04-18 00:00:00, Price To: 2020-04-18 23:59:00.","parameters":["117890","0","2020-04-18 00:00:00","2020-04-18 23:59:00"]},{"message":"The product that was requested doesn't exist. Verify the product and try again. Row ID: SKU = 117890, Store ID: 0, Price From: 2020-04-18 00:00:00, Price To: 2020-04-18 23:59:00.","parameters":["117890","0","2020-04-18 00:00:00","2020-04-18 23:59:00"]}]",
   "status": 1,
   "result_message": "Service execution success Magento\Catalog\Model\Product\Price\SpecialPriceStorage::update",
   "error_code": null
   }
   ],
   "user_type": 1,
   "bulk_id": "74bf51dc-60ea-4815-8e7c-047f7a7bdfbb",
   "description": "Topic async.magento.catalog.api.specialpricestorageinterface.update.post",
   "start_time": "2020-04-15 09:45:27",
   "user_id": 2,
   "operation_count": 1
   }

[m2-assistant]

Hi @bjornmeat. 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.4-develop instance - upcoming 2.4.x release

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

@bjornmeat 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.

[bjornmeat]

@magento give me 2.4-develop instance

[magento-engcom-team]

Hi @bjornmeat. Thank you for your request. I'm working on Magento 2.4-develop instance for you

[magento-engcom-team]

Hi @bjornmeat, here is your Magento instance.
Admin access: https://i-27865-2-4-develop.instances.magento-community.engineering/admin_232e
Login: cbf39616 Password: 70a57e5239eb
Instance will be terminated in up to 3 hours.

[m2-assistant]

Hi @nuzil. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).

  Details

  If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.

• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.

• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.

• 4. Verify that the issue is reproducible on 2.4-develop branch

  Details

  - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
  - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
  - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

• 5. Add label Issue: Confirmed once verification is complete.

• 6. Make sure that automatic system confirms that report has been added to the backlog.

[bjornmeat]

Some screenshots from db tables magento_operation and magento_bulk

[bubasuma]

Internal Magento team is working on this issue right now.

[m2-assistant]

Hi @bubasuma. Thank you for working on this issue.
In order to make sure that issue has enough information and ready for development, please read and check the following instruction: 👇

• 1. Verify that issue has all the required information. (Preconditions, Steps to reproduce, Expected result, Actual result).
     Details

     If the issue has a valid description, the label Issue: Format is valid will be added to the issue automatically. Please, edit issue description if needed, until label Issue: Format is valid appears.
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue. If the report is valid, add Issue: Clear Description label to the issue by yourself.
• 3. Add Component: XXXXX label(s) to the ticket, indicating the components it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
     Details

     - Add the comment @magento give me 2.4-develop instance to deploy test instance on Magento infrastructure.
     - If the issue is reproducible on 2.4-develop branch, please, add the label Reproduced on 2.4.x.
     - If the issue is not reproducible, add your comment that issue is not reproducible and close the issue and stop verification process here!

---

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