Cloudflare: reason can now return "filter_limit"

What changed

Producer-side tools call this additive. It breaks exhaustive switches, strict parsers and generated client enums.

Affects result.unresolved_terms[].reason on POST /accounts/{account_id}/cloudforce-one/v2/priority-intelligence/filters/generate.

New value: filter_limit.

can now return "filter_limit"

Who is affected

Code that reads POST /accounts/{account_id}/cloudforce-one/v2/priority-intelligence/filters/generate (result.unresolved_terms[].reason).

Before and after

Where	Before	After
POST /accounts/{account_id}/cloudforce-one/v2/priority-intelligence/filters/generate · result.unresolved_terms[].reason	"branch_limit", "indicators_not_supported", "invalid_keyword", "no_matching_category", "no_matching_field", "unknown_category", "unknown_country", "unknown_industry"	"branch_limit", "filter_limit", "indicators_not_supported", "invalid_keyword", "no_matching_category", "no_matching_field", "unknown_category", "unknown_country", "unknown_industry"

Code that breaks

switch (response.result.unresolved_terms[0].reason) {
  // existing branches …
  // no branch for "filter_limit"
  default:
    throw new Error("unexpected reason");
}

Based on Cloudflare’s published API specification. How severity is decided.