step can now return "clean", "extract", "filter", "pull"

What changed

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

Affects result.steps[].step on POST /accounts/{account_id}/cloudforce-one/v2/threat-signals/articles/{article_id}/reprocess.

New values: clean, extract, filter, pull.

can now return "clean", "extract", "filter", "pull"

Who is affected

Code that reads POST /accounts/{account_id}/cloudforce-one/v2/threat-signals/articles/{article_id}/reprocess (result.steps[].step).

Before and after

Code that breaks

switch (response.result.steps[0].step) {
  // existing branches …
  // no branch for "clean"
  // no branch for "extract"
  // no branch for "filter"
  // no branch for "pull"
  default:
    throw new Error("unexpected step");
}

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