{"version":"2.1.273","anchor":"history-upload-telemetry-event-name-generalized-for-reuse-be","canonical_anchor":"history-upload-telemetry-event-name-generalized-for-reuse-be","heading":"History-upload telemetry event name generalized for reuse beyond forking","tier":"internal","area":"Remote Control","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273\/e\/history-upload-telemetry-event-name-generalized-for-reuse-be","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.273","markdown":"### History-upload telemetry event name generalized for reuse beyond forking\n\nHistory-upload telemetry can now log under different event names, not just fork_conversation\n\n**What**\n\nThe internal helper that uploads a session's transcript history to a remote session, and reports telemetry when events get dropped in the process, used to always log under the fixed name `rc_fork_conversation`. It now takes the event name and a caller-supplied label as parameters instead, so different callers can report under different names.\n\n**Why**\n\nThis lets other features besides conversation forking reuse the same history-upload code while still getting accurate, correctly-labeled telemetry.\n\n- Area: Remote Control\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}