-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Maximum shipping amount allowed to refund is: €0.00 #38134
Comments
Hi @brmor-mistermenuiserie. Thank you for your report.
Join Magento Community Engineering Slack and ask your questions in #github channel. |
This issue is due to credit memo status is not checked in getCreditMemoCollection loop. |
Hi @engcom-Bravo. Thank you for working on this issue.
|
Hi @engcom-Dash. Thank you for working on this issue.
|
@magento give me 2.4-develop instance |
Hi @engcom-Dash. Thank you for your request. I'm working on Magento instance for you. |
Hi @engcom-Dash, here is your Magento Instance: https://7150201c4f9097abfaabe473562433a3.instances-prod.magento-community.engineering |
Hi @brmor-mistermenuiserie
Can you please let us know if you are using any specific third party extensions or custom code inorder to perform the above step? Thanks |
Kindly provide latest update on this comment #38134 (comment) still you are working on this issue if you are able to reproduce the issue please elaborate the steps to reproduce.Please let us know still if you are facing any issue. Thanks. |
We have noticed that this issue has not been updated since long time. Hence we assume that this issue is fixed now, so we are closing it. Please feel to raise a fresh ticket or reopen this ticket if you need more assistance on this. Thanks. |
Preconditions and environment
Magento version : 2.4.6p3
Steps to reproduce
Expected result
Credit memo is created and shipping fee refunded.
Actual result
An error after create Credit memo
![image](https://private-user-images.githubusercontent.com/103111614/279119212-798ab8a0-eb4f-4fb6-8b98-cde740f6e24b.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkyOTQwNjYsIm5iZiI6MTczOTI5Mzc2NiwicGF0aCI6Ii8xMDMxMTE2MTQvMjc5MTE5MjEyLTc5OGFiOGEwLWViNGYtNGZiNi04Yjk4LWNkZTc0MGY2ZTI0Yi5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjUwMjExJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI1MDIxMVQxNzA5MjZaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1mNGYwOThjMTBhNmRmNWM5OTVmYjU1NDZkYTJlODVkMDA4MGRjMWMzMDExOWY1MjdiYzgxMjhmMmU0MjMzYWU4JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCJ9.-dfj3RZhU5ZgCyYbRDG5V1mNzmBfJlcDD6WBLxNR9Z0)
Additional information
No response
Release note
No response
Triage and priority
The text was updated successfully, but these errors were encountered: