replied on December 18, 2019
We would probably need some more details about why the process is terminating. If you go into the instance monitoring, highlight the terminated instance, then click the little clipboard icon near the top right it should give you the actual error message so you can determine what needs to be fixed.
My first suggestion would be to always have a "default" path on your gateways. One of the most common reason for errors in a process design like this is that no valid path could be identified. By setting a default outflow path you ensure that kind of situation will not occur.
For example,
If I have the following outflow paths:
- If Field1="Yes"
- If Field2="No"
And for whatever reason the process comes through with a value of "Maybe" then it will terminate because it has nowhere to go in the gateway.
Ideally, you should always have at least one default path so that won't happen. You could either add a third branch with a default path that does something entirely different, or just decide which path you'd prefer be taken in an "unexpected" situation and set that as the default.
For example,
- If Field1="Yes"
- Default (i.e., any value other than "Yes")