What is true about Exception Handlers inside an Action flow?

The statement regarding Exception Handlers within an Action flow accurately reflects the functionality of OutSystems. Exception Handlers are specifically designed to capture and manage errors that occur during the execution of an Action. Their primary purpose is to allow developers to define a separate flow that executes when an error arises, thus ensuring that the application can react gracefully to issues rather than failing unexpectedly.

One critical aspect of Exception Handlers is that they maintain a distinct separation from the main execution flow of an Action. This means that once an error is caught by an Exception Handler, the flow defined within it cannot intersect or interleave with the flows of the original Action. Instead, the Exception Handler serves as a separate pathway that only activates in response to exceptions, ensuring a clean handling of errors without disrupting the regular flow of logic.

Understanding this characteristic is essential for structuring robust and maintainable applications, as it clarifies how errors are managed without interfering with normal execution flows, reinforcing the principle of separation of concerns in software design.