Automation debugging "no traces found" after reboot

Configuration
1

Since very recently I have a weird problem with one automations.
It triggers when I reboot home assistant (HAOS install) even though all triggers to or from “unavailable” are excluded. This is happening on the “way down” right after clicking reboot, not on the “way up”.

When I tried to analyze the situation after the reboot was completed I realized that this and almost all other automations have no traces.
Some however (around 5 out of 30) do have traces from before the reboot.
All automations are defined in yaml and have an id.

IIRC in the beginning traces were not persistent on reboot, but this changed quite a while back.

What’s going on?

2

Forget about it.

Two automations were missing an id. It seems this was was also prohibiting most other automations from persisting their traces.
After supplying an id to them, all automations have traces after a reboot again.

Unfortunately this does not help with my initial problem, because the execution of the automation in question can not persist it’s trace because of reboot.