I was able to forward this to the team and we found the issue. It looks like the current interaction setup has a class-based show/hide while in the same step it also has a show/hide affecting a single element for the same class:
Instead, you can separate this last hide/show into it’s own action step:
The interaction will still take the same amount of time as show/hide has a 0 second duration.