Zoom: recording_type can now return "archive_poll", "archive_qa"

What changed

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

Affects meetings[].archive_files[].recording_type on GET /archive_files.

New values: archive_poll, archive_qa.

can now return "archive_poll", "archive_qa"

Who is affected

Code that reads GET /archive_files (meetings[].archive_files[].recording_type).

Before and after

Where	Before	After
GET /archive_files · meetings[].archive_files[].recording_type	"aic_conversation", "audio_only", "audio_transcript", "chat_file", "chat_message", "closed_caption", "shared_screen_with_speaker_view"	"aic_conversation", "archive_poll", "archive_qa", "audio_only", "audio_transcript", "chat_file", "chat_message", "closed_caption", "shared_screen_with_speaker_view"

Code that breaks

switch (response.meetings[0].archive_files[0].recording_type) {
  // existing branches …
  // no branch for "archive_poll"
  // no branch for "archive_qa"
  default:
    throw new Error("unexpected recording_type");
}

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