You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for raising this issue, and for elaborating to such an extent.
I will take this discussion to our team to see if and how we should act if a situation like this occurs.
I shall get back to you on this ticket once we've decided.
Most projects have "auto-failing" enabled of orders to free up inventory for people not finishing their order within a certain timeframe.
In one of our projects we hade the following scenario with this setting:
Scenario
Solution
Also check for the "failed" status and automatically attempt to do an "undo" (https://documentation.b2c.commercecloud.salesforce.com/DOC1/topic/com.demandware.dochelp/DWAPI/scriptapi/html/api/class_dw_order_OrderMgr.html?resultof=%22%6f%72%64%65%72%6d%67%72%22%20#dw_order_OrderMgr_undoFailOrder_Order_DetailAnchor) and attempt to place it after the undo.
There are scenario's where the product might have already been sold out, so error handling during placing the order still needs to be in place.
Likelihood of scenario
Quite small, we have not seen it happen often that a notification is sent to late.
Payment method: directEbanking
adyen-salesforce-commerce-cloud/src/cartridges/int_adyen_SFRA/cartridge/scripts/adyenService.js
Line 42 in b4cfd7d
The text was updated successfully, but these errors were encountered: