{"version":"2.1.290","anchor":"session-events-fetch-error-now-reports-http-status","canonical_anchor":"session-events-fetch-error-now-reports-http-status","heading":"Session-events fetch errors now show the HTTP status code","tier":"notice","area":"Cloud Sessions","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/session-events-fetch-error-now-reports-http-status","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Session-events fetch errors now show the HTTP status code\n\nWhen fetching session events fails, the error now reads \"Failed to fetch session events: HTTP\" followed by the status code\n\n**What**\n\nWhen Claude Code fails to fetch the events for a session, the error message now includes the HTTP status code, the number a server sends back to say what went wrong (for example 404 or 500). The message reads `Failed to fetch session events: HTTP` followed by that number.\n\n**Why**\n\nThe earlier message used a status description that was often empty and drew on the wrong value, so it frequently told you nothing. The status code makes the failure easier to understand and report.\n\n- Area: Cloud Sessions\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}