Triggers

TonyaMallard​: As AndrewBlemings-​ pointed out, the slide is more complicated than it needs to be. 

Here's my solution for your custom Next button: 

Delete this trigger.  

Instead, set the Initial state of the button to Disabled. 

When a user returns to the slide, the "Resumed saved state" setting will show the button in whatever state it was in when the user left the slide. 

By the way, the programming assumes that the user will click a card and then click it again on the associated layer to run additional triggers. However, I don't think that's intuitive. As a user, I wouldn't bother re-clicking a card after I flipped it. In fact, I'd want to see all of the risk factors at the same time. So I suggest you rethink the interaction.

One other note: when working with variables, it's a good idea to show the variable references on the slide during development. That let's you see whether or not the values change as expected. If the user doesn't need to see the values, you can hide or delete the textbox with the references before publishing.