{"version":"2.1.225","anchor":"code-session-create-and-poll-failures-are-classified-by-reas","canonical_anchor":"code-session-create-and-poll-failures-are-classified-by-reas","heading":"Code-session create and poll failures are classified by reason","tier":"notice","area":"Sessions","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225\/e\/code-session-create-and-poll-failures-are-classified-by-reas","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.225","markdown":"### Code-session create and poll failures are classified by reason\n\nCode session failures are now sorted by cause, so retries and error messages make more sense.\n\n**What**\n\nHTTP failures from the code-sessions endpoints are now sorted into transient, terminal and auth categories instead of being treated uniformly, which changes what gets retried and what gets reported.\n\n**Details**\n\n- 401 becomes a non-terminal `oauth_rejected`.\n- 408, 429 and 5xx remain transient and are retried.\n- Anything else becomes terminal `request_rejected`.\n- Grouping and project rejections are tagged `grouping_rejected` and get their own message about the Project being unavailable.\n- OAuth-rejected session creation feeds a distinct telemetry path.\n\n**Evidence**\n\n`v2_session_create_oauth_rejected`\n\n- Area: Sessions\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 0\/5"}