radar rule limit reached: cannot add new fraud rule

TL;DR

Hitting the Radar rule limit is a housekeeping problem, not a reason to delete live protection at random. Audit the rule set first: most accounts carry disabled duplicates, test rules left in live mode, and five narrow rules that one rule with a value list or an OR condition can replace. Consolidate those, archive what is truly dead with an export, and the new rule fits with coverage intact.

radar rule limit reached: cannot add new fraud rule

Use this when

• Radar shows a rule limit message when you try to save a new rule.
• The rule list contains old campaign, test, or duplicate rules.
• Several rules differ only by one value such as a country or BIN range.

Not for this skill when

• A single rule is too complex to save. That is an editor or syntax problem, not the account cap.
• You hit a value list item quota. Consolidate list items instead of rules.

Steps

1. Export or screenshot every rule with its action, condition, and last triggered date from the Radar rules analytics. Verify: you have an inventory showing which rules actually fired in the last 90 days.
2. Disable, do not yet delete, rules that never fired and duplicate another rule, and note the change date. Verify: the disabled set is documented and live coverage rules stay enabled.
3. Merge narrow sibling rules into one rule using OR conditions or a value list for the varying field, keeping the same action. Verify: one consolidated rule covers the same test payments the sibling rules covered.
4. Save the new rule that was blocked, now that headroom exists, and put it in the intended position in the evaluation order. Verify: the new rule saves without the limit error.
5. Delete the disabled duplicates after a full business cycle with no coverage complaint, and keep the export for rollback. Verify: the final rule count sits comfortably below the cap with the export archived.

Variant phrasings

cannot create new radar rule limit

Save error phrasing.

too many stripe radar rules how to consolidate

Consolidation phrasing.

radar rules cap reached cleanup

Cleanup phrasing.

Compatibility: Stripe Radar for Fraud Teams. Rule limits are account level and shared across block, review, and allow rules, so cleanup in any one action type frees space for the others.

Why it happens

Rule sets grow by accretion: a rule per incident, per campaign, per country, and test rules promoted and forgotten. The cap counts them all. Because Radar evaluates conditions cheaply, consolidation rarely costs detection quality, while deleting a live rule at random costs real coverage.

Edge cases / pitfalls

• Rule order matters for review and block precedence. Photograph the order before consolidating and restore it after.
• Allow rules count toward the cap too, and deleting an allow rule can start blocking good customers. Consolidate allows with extra care.
• Seasonal rules, for example holiday velocity rules, should be disabled off season rather than deleted and rebuilt.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_KJJhr5WiueF8giI1LYLAQg