The info.magnolia.ui.contentapp.action.ChainedAction#ChainedAction currently keeps executing actions irrespective of whether there is a failure (validation) in an Action.

In order to prevent further validation checks on dependent actions, failing actions have two choices - either duplicate validation logic or throw an Exception.

Throwing Exception propagates all the way to the parent UI as RpcInvocationException for a very simple thing such as form validation failure. In order to avoid this behavior, the action sequence has to duplicate this validation in subsequent actions, which has it's own side effects of code duplication and suboptimal performance due to dependent ActionDefinition objects created and executed each time the chain sequence is executed.