Affected versions

• 82.0a1 (20200915092930)
• 81.0 (20200917005511)
• 80.0.1 (20200831163820)

Affected platforms

• Windows 7x64

Steps to reproduce

1. Install Firefox and open Task Scheduler.
2. Open Fiddler and change system time with 24h ahead.

Expected result

• POST that starts with https://incoming.telemetry.mozilla.org/submit/default-browser-agent/1/default-browser/ with a unique ID at the end is displayed in Fiddler.

Actual result

• Nothing happens. No post in Fiddler and no last run time is displayed in Task Scheduler for Default Browser Agent.

Regression range

• I will search for one ASAP.

Notes

• Attached a screen recording.
• The ping is correctly sent if Run is selected from the task scheduler for the default browser agent.

Suggested Severity: S3

Bugbug thinks this bug should belong to this component, but please revert this change in case of error.

After further discussing with atrif, we successfully made the task to run automatically. Windows 7 will not run the task if the time will be set past the exact minutes and seconds was installed a day earlier, while Windows 10 will run the tasks even if the date was set past that exact time.

This can be closed eventually or find a method to run the task on Windows 7 even if the user's PC was launched after the task's install time.

Not a regression. The issue is reproducible with 75.0 (20200403170909) on Windows7x64 by following the above steps and setting the date after the initial run there is no telemetry sent.

(In reply to Catalin Sasca, QA [:csasca] from comment #2)

After further discussing with atrif, we successfully made the task to run automatically. Windows 7 will not run the task if the time will be set past the exact minutes and seconds was installed a day earlier, while Windows 10 will run the tasks even if the date was set past that exact time.

This can be closed eventually or find a method to run the task on Windows 7 even if the user's PC was launched after the task's install time.

I don't know enough about the agent to be able to tell if this means we should just close this, or if there's work left here. :bytesized, can you help triage, as it appears you've worked on the default browser agent?

It's not ideal that this is the way the Window 7 task scheduler works, but (a) users changing their clock frequently isn't really an expected behavior, and (b) we have no control over the internal mechanisms of the task scheduler. Given that, I don't think there is much else to be done here.