{"version":"2.1.225","anchor":"streaming-read-index-no-longer-skips-messages","canonical_anchor":"streaming-read-index-no-longer-skips-messages","heading":"Streaming read index no longer skips messages","tier":"notice","area":"SDK Transport","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/streaming-read-index-no-longer-skips-messages","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### Streaming read index no longer skips messages\n\nMessages sent after a conversation reset or a cancelled request are no longer silently dropped.\n\n**What**\n\nTwo index bugs in the input-stream loop are fixed, so messages after a reset or a cancelled request are not silently dropped.\n\n**Details**\n\n- The read index is reset whenever a `conversation_reset` event appears in the pending batch, instead of only when a filtered condition held.\n- When a cancelled request's placeholder text message is spliced out, the read index is decremented if it sat past the removal point.\n\n**Evidence**\n\n`conversation_reset`\n\n- Area: SDK Transport\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 0\/5"}