Hi all,
I have a problem regarding error handling in my project (Re-Framework). I have inputed logic considering max consecutive system exception, but when the max number of exceptions (set in Config file) is reached, the process is stopped and message is thrown, but the orchestrator marks the test as ‘passed’ not ‘faulted’. Any ideas why this happens ? Any help will be much appreciated.
Do you get the system exception in Initialization state?
If yes, any system exception is thrown in Initialization state the bot will directly move to end process state and execution ends.
Hope it helps!!
Make sure that within the “Set Transaction Status” workflow (usually in the “Process.xaml” file), there is logic to set the transaction status to “Failed” when an unhandled exception occurs.
Where are you doing it?
If the exception thrown is inside try catch or is being handled then the process will be successful only but you would see exception in logs…thats the best practice as well…if you dont want that thwn when exception is there throw it from the main sequence and dont put a try catch around
Cheers
In your case you can configure it according to your needs.
Best Practice in Re-Framework:
If an exception occurs within a try-catch block in initilization state or is being appropriately handled, the process will still execute successfully. However, the exception will be logged for reference. This approach ensures robustness and transparency in the workflow
@Anil_G @mkankatala
It’s being done in ‘If’ loop in Initialization
yes, it should be handled, there. Thanks
If you see whole of initialize should be in try catch…so the exception is caught and handled
cheers
@Anil_G @mkankatala @Nitish_Singh @19learningcurve
I think i found out what might be the issue. My process doesn’t use Queue and in ‘SetTransactionStatus’ framework (whether Success, Business Exception or System Exception), the try catch loop refers to ‘OrchestratorQueueFolder’. What kind of logic would you suggest to use to avoid refering to any part of queue and being able to set the transaction status properly ?
then you need to change your transactionitem type and that can be avoided
if that is not changed then remove the set transaction status activity
cheers
Okay @zbigniew.wichlacz
With out using queues are you using Excel in the transaction item.
i’m working with config file to get data and input them into SAP application.
To what type should i change Transactionitem then ? Data Row ?
are you not using transactionitem at all?
if yes then just change it to string that should suffice
cheers
Okay @zbigniew.wichlacz
Where you are getting the input data, the input is in the Excel right…
Ok, thank you, TranscationItem variable has been changed to ‘string’ and i reestablished my workflows .
However i still have the same problem - when the bot reaches max consecutive system exceptions it throws the new exception, but marks the process as Succesful. I still don’t know how to fix that 
@mkankatala @Anil_G @19learningcurve @Nitish_Singh
Thank you guys, all your replies were very helpful. Fortunatelly i was able to resolve the issue.
