[Issue] Issue #13952 - Duplicate orders with same Quote Id at same time with few time difference.

[m2-assistant]

This issue is automatically created based on existing pull request: #35139: Issue #13952 - Duplicate orders with same Quote Id at same time with few time difference.

---

Description (*)

Two different orders have been placed with very few seconds as time difference with same quote Id.

Fixed Issues (if relevant)

1. Fixes Duplicate orders with same Quote Id at same time with few time difference. #13952

Manual testing scenarios (*)

1. Login as a User
2. Add items to cart and proceed through checkout.
3. Select Any payment method. Not click on place order button
4. Now login to the same account in another system.
5. And proceed to checkout with the same items. Not click on place order button.
6. Now you have to click on place order at the same time with both the systems.
7. one of the screen must return failed
   

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
• All automated tests passed successfully (all builds are green)

[m2-assistant]

Hi @engcom-Lima. 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.

[engcom-Alfa]

As tested and mentioned in the PR_comment, confirming this issue!

[github-jira-sync-bot]

✅ Jira issue https://jira.corp.adobe.com/browse/AC-6057 is successfully created for this GitHub issue.

[m2-assistant]

✅ Confirmed by @engcom-Alfa. Thank you for verifying the issue.
Issue Available: @engcom-Alfa, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.

[engcom-Hotel]

Hello,

As I can see this issue got fixed in the scope of the internal Jira ticket AC-6057 by the internal team
Related commits: https://github.com/magento/magento2/search?q=AC-6057&type=commits

Based on the Jira ticket, the target version is 2.4.6.

Thanks

[kanhaiya5590]

Hi @engcom-Hotel,

What is the solution for the lower version (< 2.4.6.) of Magento?

If there also same issue, any solution for that or any Magento patch, we can use.

[Vitancourt]

Hello @engcom-Hotel, is there a patch for versions < 2.4.6?