Issue
Multiple replacement objects are being applied to the same element (for example, several states on a single button), causing unexpected behavior.
Cause
Replacement objects are designed for a one-to-one relationship — one normal element and one replacement object. Layering multiple replacements on the same element isn’t supported and can cause activation conflicts.
Solution
Use one replacement object per element, or use multiple screens to represent different states.
To set up a replacement object correctly:
Keep the original element in its normal state.
Create one replacement object to represent the alternate state.
Add an Activate Replacement Object action to the trigger (e.g., a button click).
If you need multiple visual states, duplicate the screen and configure each version with the appropriate replacement object instead.