Failure codes
When a run fails, the alert names a stable code, not a stack trace. The code tells a developer which part of the purchase broke before they open anything.
← All docs · Updated 2026-09-04
The categories
Failures map to one of ten categories: STORE (the storefront itself is unreachable or erroring), PRODUCT (the test product is missing, out of stock or not purchasable), CART (add-to-cart failed or the cart contents are wrong), CHECKOUT (the checkout will not load or advance), SHIPPING (no shipping methods, or the method cannot be selected), TAX (tax is missing or wrong), PAYMENT (no payment methods, or the payment step errors), ORDER (order placement failed or the created order is wrong), NETWORK (a request on the path failed) and INTERNAL (a fault in MageSentinel itself, not your store).
The canonical list lives in the monitoring engine and every failure resolves to exactly one code. A run never reports a raw exception message as its result.
Why codes instead of messages
A stable code is triage. "PAYMENT: no methods available" and "CHECKOUT: shipping step did not render" point a developer at different systems immediately, and they stay comparable across runs so you can see when a failure started and whether it is the same one recurring.
Codes are also what incident correlation groups on: repeated runs failing with the same code on the same store become one incident, not fifty alerts.