Affected versions

• 80.0b1
• 81.0a1(20200729213824)

Affected platforms

• Windows 7x64
• Windows 10x64
• Windows 10aarch64

Steps to reproduce

1. Install FF.
2. After the installation process is done, access Task Scheduler.
3. Expand the Task Scheduler Library
4. Click on the Mozilla Folder.
5. Right Click on the Firefox event and click Run.

Expected result

• In Fiddler, the POST that starts with:
  "https://incoming.telemetry.mozilla.org/submit/default-browser-agent/1/default-browser/xxxxxx" si displayed instantly.

Actual result

• No POST event is displayed in Fiddler, thus information about default browser is not being sent.
• Last Run Result remains in the same state.

Regression range

• This seems like a very recent regression since I am unable to reproduce it in 79.0. Will return with regression range ASAP.

Additional notes

• This issue does not reproduce on the latest 79 release build.

• (task scheduler)Last Run Result has the following messages and errors :

• (0x0)
• (0x41303)
• The task has not run yet(0x41303) - even though the task was manually run

• Because of this issue, we are unable to test the WDBA Notifications and Kill Switch features because notifications are not shown so I would consider it an S1.

• Editing the time of the schedule has the same faulty behavior.

• The only FF event triggered is "GET /v1/buckets/main/collections/windows-default-browser-agent/records/state HTTP/1.1"

• Video attachment of the issue: https://drive.google.com/file/d/1JuTv-_PlDbPHZR-ydIZDG7f2YaGml5Bf/view?usp=sharing

• Fiddler Session Archive: https://drive.google.com/file/d/13QQ0oB7xAXjB_RkwwkNE4UnkOXxf0elR/view?usp=sharing

I tried this with 80.0b1 and I am unable to reproduce the problem; I saw the telemetry as expected. Are you sure you aren't getting hung up by the requirement to only send a ping every 24 hours? To be sure, when you try again next, could you please do these things:

• Open the Registry Editor
• Navigate to HKEY_CURRENT_USER\SOFTWARE\Mozilla\Firefox\Default Browser Agent
• Locate a registry value named "LastPingSentAt"
• If it exists, copy the data that it contains
• Note the exact system time that Windows reports
• Try running the task again and verify that you still see the same behavior as before (a ping is not sent)

Afterwards, let me know the registry data and the time that you looked up.

• (task scheduler)Last Run Result has the following messages and errors :

• (0x0)

I believe that is a success code. That doesn't seem like a problem.

• (0x41303)
• The task has not run yet(0x41303) - even though the task was manually run

Did you refresh the task scheduler after you ran the task? It does not refresh automatically. And it doesn't really make sense that we would somehow access the remote settings endpoint without running the task, so I suspect that it is indeed running properly.

• Because of this issue, we are unable to test the WDBA Notifications and Kill Switch features because notifications are not shown so I would consider it an S1.

You only mentioned telemetry issues up until this point. Is there also a problem with the notifications?

• Editing the time of the schedule has the same faulty behavior.

Manually editing the schedule isn't part of our requirements, nor is the Task Scheduler our feature. So I doubt there is much we can do here. But what faulty behavior do you mean?

There's one other thing that would help with troubleshooting. After attempting to run the task, could you open the Event Viewer, navigate to Windows Logs->Application, and see if the task produced any events. Their source would be listed as "Firefox Default Browser Agent" or "Firefox Nightly Default Browser Agent". The output that I am interested in for each event can be found under "EventData" when you click on the "Details" tab.

Note that, like the Task Scheduler, the Event Viewer does not automatically refresh, and may need to be refreshed manually if the task is run after the viewer is opened.

Looked over and I see the ping too once every 24h. It's safe to close this.