Duplicate orders with 2 parallel GraphQL requests

[github-jira-sync-bot]

Precondition

As a Guest user follow steps by GraphQL checkout tutorial to step 10 Place order https://devdocs.magento.com/guides/v2.4/graphql/tutorials/checkout/index.html

Steps

Execute Place the order mutation in parallel in 2 browsers (I did it in Postman) .

mutation {
  placeOrder(input: {cart*id: "{ CART*ID }"}) {
    order {
      order_number
    }
  }
}

(x) Actual result

2 orders created

(/) Expected result

1 order created

[github-jira-sync-bot]

The issue was exported from the internal Jira. The link to the original Jira issue: https://jira.corp.adobe.com/browse/ACP2E-1194

[m2-assistant]

Hi @github-jira-sync-bot. Thank you for your report.
To speed up processing of this issue, make sure that you provided the following information:

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

Make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:

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

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.

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

[chittima]

Issue is fixed and here is the commit:
18bdb6a