What is a key restriction of Action flows in OutSystems?

In OutSystems, action flows are designed to be structured in a way that enables clear execution paths and logical sequences. The key restriction that an action flow can have only one Start node ensures that each execution is initiated from a singular point, making it easier to track the flow of logic and manage the execution within the application.

Having a single entry point simplifies the control of the action flow and supports predictable behavior. If multiple Start nodes were allowed, it could lead to complex interactions and increased difficulty in debugging and maintaining the flow, as there would be multiple potential entry points that could vary the behavior.

This restriction promotes better design practices by making sure that the flow of actions is organized and streamlined. Other options related to multiple start nodes, the need for return values, or exception nodes do not reflect the fundamental rules governing the structure and execution of action flows in OutSystems.