{"version":"2.1.296","anchor":"teleport-events-fetch-now-fails-loudly-instead-of-returning","canonical_anchor":"teleport-events-fetch-now-fails-loudly-instead-of-returning","heading":"Loading a session's history now shows an error instead of failing silently","tier":"notice","area":"Resume","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/teleport-events-fetch-now-fails-loudly-instead-of-returning","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Loading a session's history now shows an error instead of failing silently\n\nFetching a session's history for resume or teleport now shows an error when it fails, instead of returning an empty or partial session\n\n**What**\n\nWhen Claude Code resumes a session or teleports one (brings a session from elsewhere into your terminal), it downloads that session's history page by page. It now stops with an error when:\n\n- the server answers with an error status\n\n- the reply is not in the expected shape\n\n- a later page is not found\n\n- it has run out of retries\n\nBefore, it returned nothing or only the pages it had downloaded so far. If the server refuses because the session needs a trusted device, Claude Code now says: \"This session requires a trusted device, and this computer isn't recognized as one.\" It also explains how to register this computer through `\/login`.\n\n**Why**\n\nA failed resume or teleport is now clearly reported. Before, you could end up with an empty or cut-short session and no sign that anything went wrong.\n\n- Area: Resume\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}