we are running the robot from orchestrator and the below scenario occurred twice since we moved it to prod.
Scenario - SAP gets disconnected and the robot just waits on the screen indefinitely without throwing any time out exception or element not found exception. we have to kill it from orchestrator. I checked the timeout value as well and its just 2 minutes. Did anyone experience similar situations, where robot runs forever and what can we do to avoid it.
i have seen this issue but i don’t know the issue.
To avoid this long run you can use stop after property in orchestrator schedules
This process runs whole day, processing each queue item and we don’t want to stop/kill after some time. Have you raised this issue to Uipath? Did you get any answer from them?
I don’t english
Answer in Japanese
We are seeing the same with SAP disconnects despite any error handling we have tried to implement for this. Is there anything new on how this could be solved?
You can do this work by add activity to check connection into SAP server ( check Ping method )… if has problem then stop program.
@Cristian_Ivan Check out this thread.
In our case the SAP connection drops randomly then a separate window pops up with the “connection dropped” message. The bot loses focus because that window is not expected. Short of checking for this window after every UI selector, has anyone else identified a way to recover?
The issue occurs more frequently during peak SAP processing times and it occurs randomly during the month. The connection always works when we log in again which is why we want the bot to gracefully recover from this error.
We can retry to check about 3 times ( 5 mins/one time ) before stop program.
Any thoughts on this UiPath?
You are responding to the thread which is almost 2 years old
“Any thoughts” on what?
Open a new thread, describe your situation and then I can have some thoughts
Best regards, Lev