-
Notifications
You must be signed in to change notification settings - Fork 210
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Order cancellation - possible race condition #1631
Comments
Hi @aligent-lturner, Thank you for reporting this issue with us. The reason why we delay the processing of the AUTHORISATION notification with I can see that the initial notification was created at 03:35, and the successful one was created at 3:45. Delaying the first one for 10 minutes didn't do the trick here and the initial notification seemed to be processed first. This seems to have caused the issue. Could you please further clarify whether this is a standalone case or have you experienced more of these? Looking forward to your reply, Kind regards, |
@RokPopov at this stage we're not sure if this is the only case, but we've definitely seen failure notifications turn up after successful ones before, which has been confusing, as the comments get added to the order out of sequence, so it looks like the order was successful, and then later unsuccessful. I guess I have a few queries:
|
We got the exact same issue on our website, so far 7 cases this happend. |
Hi guys, Are you also seeing the Thanks, |
Yes! |
In that case both
I will close this issue for now. However, if the problem persists feel free to leave a message in this issue which we will check, to verify if the issue should be re-opened or not. Thanks, |
Describe the bug
A scenario has been found where an initial payment failure has resulted in an order being incorrectly cancelled. This is seemingly either a race condition or a bug with how the failure notification is handled.
To Reproduce
Steps to reproduce the behavior:
payment_review
status).closed
status instead ofprocessing
Expected behavior
The initial payment failure should not result in the order being cancelled, as the order was not yet created.
Magento version
2.3.4
Plugin version
7.3.7
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
Additional context
Note that this is happening in an environment with a custom checkout, but in any case, the order should not be created in the case of an invalid card number, so why is it attempting to cancel the order?
The text was updated successfully, but these errors were encountered: