# [Distribution ID by ping reason](https://sql.telemetry.mozilla.org/queries/78152/source) Vast majority of "overdue" pings are missing the distribution ID. Low numbers for "reschedule" and "tomorrow". Still higher for "today" and "upgrade". # [Distribution ID in overdue pings](https://sql.telemetry.mozilla.org/queries/78185/source) The vast majority of "overdue" pings lack other "application"-lifetime metrics. This suggests that our logic clears application-lifetime metrics too early, before an "overdue" ping is sent. I have not yet tested this further. We do have [a test that should ensure this works](https://github.com/mozilla/glean/blob/9209b6853dbe923f1823d7a9294efca10645a1a0/glean-core/android/src/test/java/mozilla/telemetry/glean/scheduler/MetricsPingSchedulerTest.kt#L762-L839).
Bug 1694343 Comment 1 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
## [Distribution ID by ping reason](https://sql.telemetry.mozilla.org/queries/78152/source) Vast majority of "overdue" pings are missing the distribution ID. Low numbers for "reschedule" and "tomorrow". Still higher for "today" and "upgrade". ## [Distribution ID in overdue pings](https://sql.telemetry.mozilla.org/queries/78185/source) The vast majority of "overdue" pings lack other "application"-lifetime metrics. This suggests that our logic clears application-lifetime metrics too early, before an "overdue" ping is sent. I have not yet tested this further. We do have [a test that should ensure this works](https://github.com/mozilla/glean/blob/9209b6853dbe923f1823d7a9294efca10645a1a0/glean-core/android/src/test/java/mozilla/telemetry/glean/scheduler/MetricsPingSchedulerTest.kt#L762-L839).