Just discovered a strange and unexplainable behavior for one of our workflows that resulted in multiple requests ending up becoming “Close (Completed)” after a successfully completed action (i.e., the ENTER_CREDIT_DATA action shown in the screenshots below) that does not actually lead to an end point.
We later discovered that the process had an error in the transition from that action - this action had only 1 transition, which had a condition that will never be met.
Thus, was it possible for the request to be automatically closed as completed because there was no path for the request to take to the next action?
BTW #1, I am not sure if this is related to the strange behavior, but I noticed that the workflow diagram shown in the “Help” screen (a portion of which is shown in the 1st screenshot below) seems to defer from that in the “Graphical view” screen (please see the 2nd screenshot below).
In the “Graphical view” diagram, the diamond on the ENTER_CREDIT_DATA transition appears to have a line bisecting it - this appears to indicate that there is an additional transition overlapping the one with the condition. Moreover, there also appears to be another transition overlapping the transition from the next action (VERIFY) to the end point (or it is the same additional transition as before but with an break point elbow hidden behind the VERIFY action).
We have confirmed that no such additional transitions were ever added in the workflow (as shown in the 1st screenshot).
BTW #2, yes, we did eventually realize that since there is only one transition from the ENTER_CREDIT_DATA action, there was actually no need for that transition to have a condition. This was the error we had discovered.
BTW #3, we are running WorkflowGen v9.3.1.
Screenshot from “Help” screen:
Screenshot from “Graphical view” screen:
