Layers not displaying correctly based on variable value

There’s nothing wrong with your logic but the setup is quite complex and heavy. The calculation itself is already intricate, and on top of that, all the different "When" events appear to be handled on a single base layer, using a large number of "OR" conditions and and placing all the heavy lifting on the Submit button. This creates a fragile system that can easily break under certain conditions.

While it's possible to patch some of the issues by hiding layers or adjusting trigger order, I don’t see that as a sustainable solution. For example, Feedback Layer 4 is being shown even when Feedback Layers 1, 2, or 3 should be displayed instead. This is likely due to its higher visibility in the layer hierarchy, combined with Storyline’s inability to process all overlapping conditions in real time, especially under the complex setup described above. Simply hiding the incorrectly displayed layer or reordering the triggers doesn’t solve the core problem. Without restructuring the logic and reducing the load on the base layer, similar issues are likely to continue occurring.

I've attached another version (Slide 2) to show how I would approach this. In this version, I created a dedicated Calculation layer that opens when the user clicks Submit.

In this setup, the base layer is responsible only for managing user input — specifically collecting PathQ values through the selection and deselection of radio buttons.

The actual evaluation logic is moved to a separate Calculation layer, which is triggered when the user clicks Submit. This layer fetches the current PathQ values, performs the necessary logic, and sets the appropriate True/False feedback variables (e.g., Feedback_1, Feedback_2, etc.) based on defined conditions.

Each feedback variable is linked to a specific scenario, and when one of these variables changes to true, the corresponding feedback layer is triggered.

By dividing responsibilities in this way:

• The base layer remains lightweight, only handling input.
• The Calculation layer performs the heavy logic, reducing the risk of conflicts or timing issues.
• Layer visibility and feedback control are handled cleanly through variable-driven triggers, rather than complex stacked conditions on the base layer.
• The Submit button no longer struggles to process everything at once, but instead has a single, clear responsibility: to show the Calculation layer.