The deployment modes on the umbrella radiator, especially in regards to automation, seem borked. This may be in relation to receiver dishes (since the Circular Thermophotovoltaic Receiver also seems weirded out similarly, albeit differently).

In previous versions, the umbrella radiator would, for instance, when automation is enabled, open up after leaving atmosphere. It would also automatically close upon liftoff (if opened), as well. Neither of these work anymore.

Additionally, if the radiator/automation/deployment modes aren't selected properly in VAB, upon liftoff the radiator won't animated that it has opened but will act like it has opened from liftoff (causing launch speed to drop, as it should when opened).

I also noticed that there are repeated actions available for this part, and some of the actions, when mapped, don't actually work.

I see that there is indeed some problem.
Automation toggles are visible only in editor (and only once. Reloading vehicle hides those. In Flight they're also not available.
I can also see that there is no Deployable Radiator module for it.
//animName = extendShield (is commented).
I don't have a clear idea what to do. Also haven't seen anything obvious in part file history.

@sswelm I will need your assistance here. Please guide me a little and I will fix this part.

There are 2 part module that control this part, which is the MicrowaveReceiver and Radiator. Both have a form of automation which might interfere with each other. The way to solve it is that one need to take control why the other becomes a slave. There should already be this behaviour be for some reason It doesn't work anymore as it supposed to.

That's quite a lot of info. I'll look into it.

It seems that the info was correct. Microwave power received does override Radiator automation. But it doesn't have automation of it's own - or rather automation is one way - only enables when possible. Won't disable if dangerous conditions are present. Automation toggles are also not visible once Radiator toggles are disabled.

Edit:
I do have an idea how to fix the issue. Enable/Disable Radiator Automation depending on the part Mode (radiator/receiver). But most likely we would also need to fix Receiver automation (to disable it when entering dangerous conditions (so full Auto implementation, since it CAN be different than that of Radiator), or to treat Receiver totally as Slave, or to implement it corretly on Receiver side and treat Radiator as Slave).