UML25 — Behavior after exceptions are encountered

In the discussion of OpaqueBehaviors in caluse 13, it is mentioned that a Behavior may be "abandoned" after it has raised an exception. The semantics of "abandonment" following exceptions are not defined, except (it seems) for the specific case of ExecutableNodes in activities.

So, is there something general that we can say in Common Behaviors about the state of a Behavior after it has encountered an exception? For example, in case of a state machine: is it meaningful for the state machine to handle an exception event after it has encountered an exception? (if so, what state is it in following an exception?)

The issue is referencing the following sentence in Subclause 13.2.3: “A FunctionBehavior may raise exceptions
for certain input values, in which case the computation is abandoned.” It is rather odd to only mention
exceptions in the specific case of FunctionBehaviors, since exceptions can potentially be raised by any kind
of Behavior. This would be better explained more generally.