A decision node in process model is not completing and getting struck there.

Question

A decision node is not completing and getting struck there. This node is not updated and the process has not changed from few days. 
 Suddenly, it is stopping at the decision node. Wondering in what scenarios it would get struck there. Suppose if there is any error, an error should be thrown on the node and we should be able see the error. But when right clicked on the node, the option to start another instance for that node is disabled and upon clicking on the node, no error is shown. 
 Please advise.

Domen Jemec · Accepted Answer

The issue here seems to be that you have 1 incoming flows to the decision node (currently not supported for XOR). "The exclusive (XOR) gateway connects one incoming path with a single outgoing path. A looping flow should not be directed into an XOR gateway itself, but into another upstream activity. For example, place an empty Script Task node between the incoming flows and the XOR node when you are routing multiple flows into the XOR." docs.appian.com/.../XOR_Node.html 
 As a workaround for a loop of this sorts, consider putting an empty script task before the incoming flows to join the two pathways from the "Check if pathway .." then have 1 connection going to the XOR.

ekanshj · Answer

Hi anushas0002 , You have two incoming paths to your decision. which cannot happen. The exclusive (XOR) gateway connects one incoming path with a single outgoing path. If you really want your decision to have two incoming paths then add a dummy script task before the decision and then pass the flow to decision from the dummy task.