In the normal modeling view it is not possible that one action can have more than one incoming or outgoing edge. This is only possible with the usage of ControlNodes such as DecisionNode, MergeNode, SplitNode and JoinNode.
However, if you select an ActivityEdge and change the from/to properties you can give an action more than one incoming and outgoing edge. This should be prohibited.
With the advent of XorControlNode and AndControlNode this problem still exists, but is only interesting for the views where DecisionNode, MergeNode, SplitNode and JoinNode are shown.