When I use the minecraft:timer component in my own addons, it seems to break/disable other components like the minecraft:behavior.move_towards_restriction component. I think it does this to the minecraft:behavior.melee_attack, and minecraft:behavior.move_to_block components as well but I couldn't make sure of this. I know its the timer that is causing this because during testing I made the timer activate later on instead of activating right away and before it activated, my mob was actually attacking me until the timer activated which afterwards the mob began to randomly stroll and forget about attacking me. I believe there's possibly other components that the timer breaks that I don't know of.

I kept wondering why my custom entities weren't attacking me like they were supposed to when I was testing them until I finally found out that removing or not having the timer running fixed this.

I use multiple component groups that use the timer in just one entity. I also don't have all of them running at the same time though. I usually just have one or two runnning while the other timers are supposed to activate later on when the component group is called. idk if that info would help in anyway