{"version":"2.1.268","anchor":"session-start-event-now-checks-whether-the-session-head-is-o","canonical_anchor":"session-start-event-now-checks-whether-the-session-head-is-o","heading":"Session-start event now checks whether the session head is orphaned","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/session-start-event-now-checks-whether-the-session-head-is-o","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### Session-start event now checks whether the session head is orphaned\n\nSession-start telemetry now checks whether the session's starting point is orphaned before firing\n\n**Unclear.** What exactly counts as an 'orphaned' session head is not specified in the evidence.\n\n**What**\n\nThe telemetry call that fires when a session starts now first runs through a helper that determines whether the session's starting point (its 'head') is 'orphaned', and passes that status along with the event, instead of always firing unconditionally.\n\n**Why**\n\nThis lets session-start tracking distinguish sessions that resume from a disconnected or missing starting point from normal ones, which is useful for diagnosing session continuity issues.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}