Order failure management for pending and failed orders
Key Takeaway
Marking a Process Exception record Resolved places a failed order again only if the Retrigger Place Order flow is active.
In B2B Commerce stores that process orders asynchronously, checkout does not always finish right away. A cart can end up Pending or Failed instead of becoming a completed order. Order failure management covers what happens next: showing those orders to buyers, releasing held inventory and coupons, reversing payments, emailing buyers, and letting an admin fix a failed order and place it again.
Failed orders in asynchronous stores
B2B stores created with the LWR template in Spring '23 or later process orders asynchronously. Asynchronous processing improves store performance and responsiveness. The trade-off is that the store can sometimes generate failed orders. Failed orders appear as PlaceOrderFailed exceptions.
When an asynchronous order fails with a PlaceOrderFailed exception, the exception is converted into a Process Exception record.