Order save() updates all fields instead of only changed ones, causing data loss in concurrent processes

[marcinfr]

Preconditions and environment

No response

Steps to reproduce

1. Load an order (e.g. via OrderRepository or model load).
2. Modify one field (for example, a staus).
3. Call save().
4. Check the executed SQL queries.

Expected result

Only modified fields should be updated in the database, so that concurrent saves do not overwrite unrelated data.

Actual result

• Magento executes an UPDATE query that includes all columns, not just the modified ones.
• This behavior causes data loss if two separate processes load two different orders and save them around the same time, because they may overwrite each other’s changes on unrelated fields.

Additional information

No response

Release note

No response

Triage and priority

• Severity: S0 - Affects critical data or functionality and leaves users without workaround.
• Severity: S1 - Affects critical data or functionality and forces users to employ a workaround.
• Severity: S2 - Affects non-critical data or functionality and forces users to employ a workaround.
• Severity: S3 - Affects non-critical data or functionality and does not force users to employ a workaround.
• Severity: S4 - Affects aesthetics, professional look and feel, “quality” or “usability”.

[m2-assistant]

Hi @marcinfr. Thank you for your report.
To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce.

• For more details, review the Magento Contributor Assistant documentation.
• Add a comment to assign the issue: @magento I am working on this
• To learn more about issue processing workflow, refer to the Code Contributions.

---

Join Magento Community Engineering Slack and ask your questions in #github channel.
⚠️ According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.
🕙 You can find the schedule on the Magento Community Calendar page.
📞 The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.

[m2-assistant]

Hi @engcom-November. 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).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

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

[engcom-November]

Hello @marcinfr ,

Thank you for the report and your collaboration.

We’ve reviewed the issue and determined that it requires development support. Accordingly, we are marking this as a Dev Experience item.

Thank you once again!

[m2-assistant]

Hi @engcom-Hotel. 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).
• 2. Verify that issue has a meaningful description and provides enough information to reproduce the issue.
• 3. Add Area: XXXXX label to the ticket, indicating the functional areas it may be related to.
• 4. Verify that the issue is reproducible on 2.4-develop branch
  Details

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

[engcom-Hotel]

Hello @marcinfr,

Thanks for the report and collaboration!

We have tried to reproduce the issue in the latest development branch i.e. 2.4-develop and it seems the issue is reproducible for us. We have created a console command to reproduce the issue as follows:

 /**
 * @inheritdoc
 */
protected function execute(
    InputInterface $input,
    OutputInterface $output
): int {
    $orderId = 9;
    $output->writeln("Getting Order ID: " . $orderId);

   
    $output->writeln("\n=== Test 1: Updating Order State ===");
    $order = $this->orderRepository->get($orderId);
    if ($order) {
        $output->writeln("Order found: " . $order->getId());
        $output->writeln("Current state: " . $order->getState());
        $output->writeln("Current status: " . $order->getStatus());
        
        // Change state - this should definitely trigger a DB update
        $order->setState(\Magento\Sales\Model\Order::STATE_PROCESSING);
        $order->setStatus('processing');
        $output->writeln("Setting state to processing and status to processing");
        $this->orderRepository->save($order);
        $output->writeln("Order saved (Test 1)");
    }
    return Command::SUCCESS;
}

When we tried to update the status the expected should update the the status column but it is trying to update all the columns. Hence confirming the issue.

Thanks