{"section":"known-issues","requestedLocale":"en","requestedSlug":"race-condition-with-get-orderform-when-user-is-authenticated-and-email-is-null","locale":"en","slug":"race-condition-with-get-orderform-when-user-is-authenticated-and-email-is-null","path":"docs/en/known-issues/Checkout/race-condition-with-get-orderform-when-user-is-authenticated-and-email-is-null.md","branch":"main","content":"## Summary\n\nGET OrderForm may run concurrently with other orderForm update requests. If, upon request, the user is authenticated, the orderForm's `email` field is `null`, the GET OrderForm will load the user's profile data to the orderForm, which may generate conflict with the result of other concurrent requests.\n\nEspecially, when the GET runs concurrently with a POST `/attachments/clientProfileData` request and finishes after it, the `clientProfileData` passed on the attachment request may be overwritten and the user's profile data loaded by the GET request will prevail.\n\n## Simulation\n\nThere is no simple way to simulate this issue, but it should happen if:\n\n\n1. User is authenticated and the orderForm's `email` field is `null`\n2. A request to POST `/attachments/clientProfileData` is made passing a different data from the user's profile\n3.\n\nA GET orderForm request is made _**before**_ and finishes _**after**_ the POST `/attachments/clientProfileData` has been finished\n\n\n\nAfter both requests are finished, `clientProfileData` should be the one from the user's profile and not the one passed on POST `/attachments/clientProfileData`\n\n## Workaround\n\nN/A"}