Automations with time triggers do not fire anymore

Hi, I'm looking for help about my C5 hubitat.

For several days now, every time triggered automation does not fire anymore, starting each night / morning. After rebooting the hub they fire up again at the right time all day long, until the next night / morning.

Before rebooting I checked the logs and the "faulty" automations : no particular issue in the logs (that I can see anyway) and every "faulty" automation is still scheduled as planned.

My free memory OS (RAM) is about 270000 when I check it.

Do some people already encounters this strange sudden behavior ? What did you do to resolve it if so ?

Thanks a lot.

Mine's been doing this for a couple of weeks now. It may have started with an update, but I was busy, and didn't really focus on it at the time.

Since it only fails overnight and a reboot restores it, I would check the hub's time and scheduled jobs before the next reboot, rather than assuming the rules themselves are broken. In Settings, confirm the time zone and current hub time are correct, then look at Logs and any scheduled jobs for the affected rules to see whether their next run time is missing or stuck in the past. If several unrelated rules all stall at the same overnight point, that pattern usually points to a scheduler or system-level issue around that time, so noting the exact time the first rule fails and whether a particular app or device was busy then would help narrow it down.

This is totally it. Every time triggered automation, even totally unrelated, are affected. It occurs between 22:30 (my last working time triggered automation) and 4:00 (my first non working one). I suspect that the overnight automated maintenance is breaking something that reboot solves.

Anyway, since the issue appeared I've thought of what change I did, and a strong suspect was that I installed and ran the custom app "Shelly device manager app". I did nothing else during this time frame. I uninstalled it but the custom app but it did nothing. Then I did a sift reset and backed up my hub to the restore file from before this custom app and it's working again.

Exactly the same happening here (including the time the trouble begins), still unsolved.