Closed nh-mdev closed 1 year ago
Hello there, @nh-mdev! It appears that I'm unable to replicate this issue directly. Could you kindly provide me with the product types you are utilizing?
I noticed that the "Rezeptgebühr" is the only item line with a price, while the first item appears to be a free item that can still be shipped. Please share the most relevant information with me so that I can reproduce and debug this issue effectively.
@Frank-Magmodules hey, my bad, i should have provided more details regarding the involved products.
The products involved in this particular case are:
A bit of domain context: These type of orders happen quite frequently. Customers can get a doctors prescription, which qualifies them to have at least one product for free, hence the 0€ for the configured product. Additionally, there is always a so called "prescription fee" associated with such a process, which is the virtual product.
Let me know if you need more input, happy to help.
Hello, @nh-mdev! I’m pleased to inform you that we have addressed this scenario in the most recent release of the Mollie plugin. We’ve made sure to cover your issue, and we hope it resolves any concerns you had. I will go ahead and close this matter for now, but please feel free to reopen it if you need any further assistance or have any other questions.
Describe the bug Whenever an order is in a shipped-/unshipped state, i.e. some items are marked as "completed" (shipped) and some as "paid" (unshipped), the webhook starts failing with an 503 "{ error: true }" exception.
Used versions
To Reproduce Steps to reproduce the behavior:
Expected behavior The webhook should work for orders with mixed items of shipped/unshipped state.
Actual behavior The webhook throws an 503 "{ error: true}" exception.
Screenshots
![image](https://github.com/mollie/magento2/assets/66021947/46ba2761-0135-4a74-9c46-ff9c7e07e5a9)
Magento error
![image](https://github.com/mollie/magento2/assets/66021947/8a7a3f03-1010-4270-8761-1885588124c8)
Additional context We upgraded from 2.22.0 to 2.26.0 on May 30th.
Never encountered this error before the upgrade.
As you can see inside the "History" screenshot, interestingly enough, the initial webhook after a first item/multiple items are shipped, succeeds. All following afterwards fail.