Hello,
In patch auto, I note that the calcul of the start date is inconsistent and different from the previous month.
Indeed, if I configure a schedule in UTC time like this, the start date isn’t logic
The 10 January is not the “4 friday + 7 days”
This is not just a visual issue, the action is realy created. In december I didnt notice that, I think this came with the new 2025 calendar.
The Webui and all my infra is in 11.0.3 version.
Do you also notice that ?
I also had a similar case - I’ve opened a case with HCL Support and they are checking it
Me too and still no solution since tuesday morning 
I don’t have a solution but a couple of interesting points.
“7 days after the fourth Friday” is the last day of the month this January.
The schedule switches from “Jan 31” to Jan 10" when we change the UTC time from 1600 to 1700:
Restarting the WebUI service does not appear to change anything on it.
I cannot comment on the issue at hand, but will contribute that global date math is hard. Hard for developers, hard for schedulers, hard for operations managers. This is true no matter if you use try to use UTC, or local time. Unexpected results are commonplace.
For example, from Your Calendrical Fallacy Is…:
No place is ever more than 12 hours away from UTC
False. Parts of Oceania are 12:45, 13:00, and 14:00 hours ahead of UTC.
(I highly recommend Your Calendrical Fallacy Is…, by the way. It’s a great for destroying expectations that calendaring is an easy problem.)
That said, this sounds like a fascinating bug deep within the scheduling logic.
Blame it on the island republic of Kiribati
Reference to deployment time documentation: Create a Patch Policy
