{"version":"2.1.228","anchor":"two-new-content-block-types-are-handled-instead-of-hitting-t","canonical_anchor":"two-new-content-block-types-are-handled-instead-of-hitting-t","heading":"Two new content block types are handled instead of hitting the unknown-type path","tier":"notice","area":"Streaming","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228\/e\/two-new-content-block-types-are-handled-instead-of-hitting-t","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.228","markdown":"### Two new content block types are handled instead of hitting the unknown-type path\n\nResponses can now include mid-conversation model-switch and system blocks without hitting unknown-type handling.\n\n**What**\n\nResponses can now contain blocks of type `fallback` (the point where the API switched models) and `mid_conv_system`. Token accounting, block dispatch and the streaming handler all handle both explicitly, counting them as \"other\" tokens and returning quietly rather than treating them as unknown. An additional 400-error classifier also now recognises the `effort_unsupported` upstream error class.\n\n**Details**\n\n- The existing `output_config` text match for that error class remains alongside the new classifier.\n\n**Evidence**\n\n`case \"mid_conv_system\":`\n\n- Area: Streaming\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 5\/5"}