Closed Skullsneeze closed 2 years ago
Hi @Skullsneeze,
Thank you for opening this issue. We are experiencing more problems in our flow upon invoicing (see #1390). They might be correlated. I have opened an internal ticket and we will be investigating shortly.
Cheers, TITUS
Hi @tnaber,
Thank for the quick reply. I think this is similar but still a different issue. I would expect an order that is captured on shipment to get the status that is configured for "Order status: payment confirmed", given the tooltip for this status says the following:
Status given to orders after capture result is confirmed by an AUTHORISATION webhook (if capture mode = immediate) or a CAPTURE webhook (if capture mode = manual capture) from Adyen.
I think the issue as I currently see it is that the manual capture which is set for the OpenInvoice payments prevents the status from being changed from Payment Review
Did some debugging in the meantime, and found this error poping up during the processing of the notification:
PHP Fatal error: Uncaught Error: Call to a member function pay() on null in vendor/magento/module-sales/Model/Order/Invoice.php:368
This means the payment can not be retrieved from the order for some reason. Will continue looking into this on my end as well and will share any updates here
@tnaber has there been any progress issue? This issue is a blocker for us moving to the latest version of the adyen module.
Hi @jordanvector,
I will increase the priority and pick this up next sprint (next week).
Cheers, Titus
Describe the bug With the "Capture on shipment for OpenInvoice Methods" setting enabled the payments do get captured within Adyen, but get stuck in the Payment Review status in Magento.
To Reproduce Steps to reproduce the behavior:
Expected behavior After the Capture notification is processed the Order status is changed to "Complete".
Magento version 2.4.2
Plugin version 8.2.1
Desktop (please complete the following information):
Additional context
The order comment that is added follows this format:
When checking the cron and notification logs I see the following:
After this the notification record in the DB is not updated anymore and is "stuck" with the processing flag set to 1 and the done flag set to 0