Component Interactions vs Global Classes: Handling Overridden Animations in Webflow

Goal: Ensure that a change to a component’s interaction (such as a hover animation) updates every placed instance, even when some instances have previously overridden that interaction.

Constraint: Webflow’s documentation indicates that when an instance’s interaction is overridden, subsequent modifications to the master component’s interaction do not propagate to that instance, causing inconsistent animation states. It is unclear whether defining interactions through Global Classes instead of component interactions avoids this limitation, or whether the only reliable approach is to refrain from overriding interactions on instances.

Should you avoid overriding interactions on component instances if you need future master updates? Can Global Classes be used to define interactions that propagate regardless of instance overrides? Is there a recommended workflow to reset overrides and regain propagation without losing instance‑specific styling?