Asynchronous order placement and the Retrigger Place Order flow
Key Takeaway
Setting a failed order's process exception record to Resolved resubmits the order, but the Retrigger Place Order flow must be active first.
B2B stores created with the LWR template in Spring '23 or later place orders asynchronously, which means in the background. Asynchronous order processing improves store performance and responsiveness, but some orders can fail later. A failure with a PlaceOrderFailed exception becomes a process exception record that a Commerce admin fixes. The Retrigger Place Order flow then places the order again.
What happens when an order fails
When an asynchronous order fails with a PlaceOrderFailed exception, the exception becomes a process exception record. A Commerce admin can then view that record and investigate the cause of the error.
The Retrigger Place Order flow is an automatic flow. After the admin fixes the problem and changes the record's status to "Resolved", the flow resubmits the order. The status change is what places the order again.
Ana is the Commerce admin for a B2B store created with the LWR template in Winter '24. The Retrigger Place Order flow is already active. A buyer named Tomas orders 200 office chairs, and the order fails in the background with a PlaceOrderFailed exception. Ana opens the process exception record, investigates the error, and fixes the cause. She changes the record's status to Resolved. The flow then resubmits Tomas's order.