Exception Handling Issue with latest community version

like for each? but already it should proceed for next as per RE framework structure

Usually if a transaction item gets failed the next will one will be processed automatically, in REFramework
So have we looped to the next case after this TRY CATCH BLOCK if so we don’t need to include that next sequence in the catch block as it would automatically go to the next case being inside a loop
Cheers @S_Srobot

exactly next one should already get to start if one fails but here it is terminating instead of fetching next transaction. I have consulted a couple of people and have been notified that there is some issue with this 19.10 version which will directly terminate any case falling to catch instead of working on the next one. But I don’t think it should happen like that. Do we need to do something to guide the flow to get iterated for next transaction? Or it will just fail, go to catch, write log file for that case as failed and itself go for next item try?

Are we running debug mode
Kindly run in normal mode and check
@S_Srobot

normal mode only we are running.

No buddy
That won’t occur buddy as that is purpose of the catch block to catch the exception and help the process to continue further
That too if we run in normal mode catch block will catch the excpetion but won’t terminate the process
@S_Srobot

that is the thing instead of catching and moving on it is terminating the flow.

Fine
Is that invoked workflow file invoking sequence has included any Termjnate Workflow activity
@S_Srobot

no terminate activity is used anywhere.