Release guards compare a candidate with the last prepared release. A surprisingly large removal count can mean the source returned a partial catalog, the wrong market, or an access-error response. A large price or availability change can be valid, but it should be checked against the business event that caused it.
The preview lists the reasons that stopped the release. Correct the input and create a fresh preview when the change is accidental. Some policies allow an explicit override; others require correcting the catalog or having the owner revise the policy. An override is a review decision, not evidence that a destination will accept the export. The previous prepared release remains available while you investigate.
What to do
- Read every guard reason and inspect added and removed item samples.
- Compare counts and prices with the original source system.
- Correct partial feeds, mappings, or unintended market changes.
- Rebuild the preview after any source, review, rule, or policy change.
- Only confirm a permitted override when the full change is intentional and understood.