{"version":"2.1.219","anchor":"api-error-assistant-messages-round-trip-through-the-sdk","canonical_anchor":"api-error-assistant-messages-round-trip-through-the-sdk","heading":"API-error assistant messages round-trip through the SDK","tier":"internal","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219\/e\/api-error-assistant-messages-round-trip-through-the-sdk","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.219","markdown":"### API-error assistant messages round-trip through the SDK\n\nResumed sessions can now still tell which past messages were API errors rather than real replies.\n\n**What**\n\nAssistant messages flagged as API errors keep that flag across serialization, so a resumed or replayed session can distinguish them from real assistant output.\n\n**Details**\n\n- Transcript serialization emits `is_api_error_message: !0` for such messages.\n- The reverse conversion maps it back to `isApiErrorMessage`.\n- This joins the existing `aborted` and `is_virtual` flags.\n\n**Evidence**\n\n`is_api_error_message`\n\n- Area: Sessions\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 0\/5"}