In the REF, in the Process.xaml file, I have an activity where I try to put some data into a queue. It will trigger an exception because there is already a duplicate in that queue. Thats all fine. However, when I trace how the exception bubbles up in the framework, I realize, that from Process Transactions, there is no way to go from this state to the End Process state.
In other words, if an exception is raised in Process Transaction state, that will eventually lead the framework to go back to the Initialization state. Once there, It will retry to the whole process.
I would really not like to do that. I would rather go to the End Process state.
What is the proper way to prevent ReFramework from looping on exception.