Currently, an interaction (e.g., a button click) on an object can only have one destination per trigger type. If a designer wants to use the exact same object in two different flows (e.g., a "Happy Path" and an "Error Path"), they are forced to either:
-
Duplicate the page, breaking the "Single Source of Truth" principle and increasing maintenance.
-
Use (page)components and instances, not ideal.
-
Use Complex Variables/Logic, which is powerful but overcomplicates simple flow branching and makes the "Prototype Settings" unnecessarily complicated.
Request
A feature where a component can have multiple destinations for the same trigger type depending on which 'Flow Starting Point' is active.