I have a very complex process or running SAP transactions with a lot of dependencies and architect,
the client I’m working for is limiting the number of SAP LogIn, that’s why I added a sequence that checks for tasks BEFORE initialization, so I won’t enter SAP for no reason,.
my problem is that when I don’t have any tasks, there is a THROW in init, which I believe causing the job state to show as FAULT in orchestrator, but business wise its ok,
any suggestions on how to make the state SUCCESSFUL regarding throw in init?
my other option is to change the location of SAP LogOn&Login to “process transaction” in framework but my process I stable now after log time and I don’t want to damage anything.
Can you share the details of job faulted?
You can get it from Orchestrator by clicking the details of faulted job, may be you will get better idea from there…
Usually job get faulted due to RDP connect lost, Credentials of machine got changed and if their is an object reference error and if it’s not even handled in Try catch block.
You should be using a Try/Catch around your code, and then the Throw will make it go to the Catch section where you can handle the error properly without showing fault in Orchestrator.
Actually we need to make SystemException having some exception value in it
because we want the bot to move to ENDSTATE if there is any exception while login instead of faulting
So the overall Init state will be in Try Catch na
Can you share us the screenshot of It or jus assign as
SystemException = True in catch block
@ermanoj3101 thats what is did and it does the work, I added log message that business exception is null . THANKS!
@Palaniyappan I’m not sure that I understood your answer, but actually
I don’t want the bot to get to END PROCESS because there are no apps to close, the fault happened in init, but I learned now the way to control the states and flow trough this screen