framgeld

Has anybody else been able to replicate this, by any chance?

This appears to have been reported back in 2016... are there any plans to fix this? If not, is there any way of me getting access to the scheduled fire...

I have just debugged this and added some breakpoint action logging, and I can confirm that the value of the **ScheduledFireTimeUtc** starts out with the correct value, but mutates to...

The issue I reported seems very familiar to this unmerged pull request: >#375 JobExecutionContext ScheduledFireTimeUtc Wrong so Misfire Detection Also Not Working