I have some rules that have multiple Groups as the Set Reaction based on different scenarios. In one instance, it's a bedroom light that has three possible "outcomes": morning, evening, and rainstormers. If I break out the ruleset into three unique rulesets each works fine.
Here's another instance that I caught tonight: porch lights that are supposed to react differently - but this time it's the Reset Reaction that's being ignored:

Here are the log entries directly tied to this but I will upload the entire log to you @toggledbits
[latest-26120]2026-05-02T01:17:35.641Z <Rule:INFO> Porch lights: brighten for guests (rule-grpvl9oypg in Outdoor Lighting, Nightly) evaluated; rule state transition from SET to 'RESET'
[latest-26120]2026-05-02T01:17:35.644Z <Engine:INFO> Enqueueing "Porch lights: brighten for guests<RESET>" (rule-grpvl9oypg:R)
[latest-26120]2026-05-02T01:17:35.655Z <Engine:NOTICE> Starting reaction Porch lights: brighten for guests<RESET> (rule-grpvl9oypg:R)
[latest-26120]2026-05-02T01:17:35.655Z <Engine:INFO> Porch lights: brighten for guests<RESET> all actions completed.
The Set Reaction for the bedroom light looks like this:

I've not had a chance to re-enable that ruleset and grab logs from it yet.