{"version":"2.1.239","anchor":"api-error-codes-are-preserved-through-stored-messages-and-fa","canonical_anchor":"api-error-codes-are-preserved-through-stored-messages-and-fa","heading":"API error codes are preserved through stored messages and failure records","tier":"internal","area":"Elsewhere","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239\/e\/api-error-codes-are-preserved-through-stored-messages-and-fa","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.239","markdown":"### API error codes are preserved through stored messages and failure records\n\nAPI error codes now survive being stored and reappear in failure records.\n\n**What**\n\nAn assistant message's API error code now survives deserialisation as `apiError`, is passed along by the failure-marking helper into the API-failure record, and a new error branch produces it for one specific error constant with a matching log line. Unconditional.\n\n**Evidence**\n\n`...(t.api_error !== void 0 && { apiError: t.api_error })`\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}