Preserve copilotTracking ID (tid) in telemetry when token is reset #3308
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes https://github.com/microsoft/vscode-internalbacklog/issues/6678
Fixes missing copilotTracking ID (tid) values in error telemetry events (e.g., [response.error] for quotaExceeded, badRequest).
When the Copilot token is reset due to HTTP 401/402/403 responses, the telemetry sender was clearing the tid value immediately. Since error telemetry is sent after the token reset, these events were missing the tracking ID.
The fix preserves the last known tid value instead of clearing it when the token becomes undefined, ensuring error events can still be correlated with the user session that made the request.