The following Firefox probes will expire in the next major Firefox nightly release: version 120 [1].

firefoxview.synced_tabs_empty#synced_tabs_empty

What to do about this:

1. If one, some, or all of the metrics are no longer needed, please remove them from their definitions files (Histograms.json, Scalars.yaml, Events.yaml).
2. If one, some, or all of the metrics are still required, please submit a Data Collection Review [2] and patch to extend their expiry. There is a shorter form for data collection renewal [3].

If you have any problems, please ask for help on the #data-help Slack channel or the #telemetry Matrix room at https://chat.mozilla.org/#/room/#telemetry:mozilla.org. We'll give you a hand.

Your Friendly, Neighborhood Telemetry Team

[1] https://wiki.mozilla.org/Release_Management/Calendar
[2] https://wiki.mozilla.org/Firefox/Data_Collection
[3] https://github.com/mozilla/data-review/blob/master/renewal_request.md

This is an automated message sent from probe-scraper. See https://github.com/mozilla/probe-scraper for details.

Tracking because browser/components/firefoxview/tests/browser/browser_tab_pickup_device_added_telemetry.js tests for this.

The bug is marked as tracked for firefox119 (nightly). However, the bug still isn't assigned.

:pluk, could you please find an assignee for this tracked bug? If you disagree with the tracking decision, please talk with the release managers.

For more information, please visit BugBot documentation.

Ethan, James, we have probes expiring for the old Firefox View as of 120. As I understand it, we only need the hold back for 119, and then firefoxview-next will be rolled out to everyone as of 120. Can you confirm we don't need to renew these telemetry probes for the old firefox view for 120?

Actually, I just realized this was a probe sfoster specifically added in bug 1809661 to see how long we wait before tabs appear. I think we can let this lapse and remove the use of it.