I have designed a flow with an optional process. This optional process does some changes to the data in the case. When we conclude the flow, it returns to the current assignment in the main flow, as expected. The problem I'm facing is when I select the cancel option on the optional process. While it does return to the current assignment in the main flow, it is duplicating my case (and there is no error message I could find in the tracer). Does anyone have any suggestions on what could be causing this behaviour?
***Edited by Moderator, Maryrita: moved to Product Support from Applications***
Can you trace with all of the rulesets and the DB Query event type? If another case is being created then you should see a commit somewhere in the trace for that new item. Then you can review the rules executed prior to that point to see what is causing it.
I solved the issue by changing it from an optional process to a local action as I needed to deliver it so we could deploy, but I'll definitely set up it on a VM to better understand the issue and will get back to you.