Some activities such as SAP.ReadStatusbar activity do not obey the Timeout property if the SAP session has hung or disconnected. It will keep running forever until the user manually kills SAP
With this snippet, you can enforce a hard timeout limit by having a separate timeout handler that runs independent of your main flow, meaning it wont get affected by events such as SAP being busy/hung. If the timeout does occur robot will kill SAP etc, which will solve the above problem
How to use?
Open Timeout handler – main.xaml
put your SAP flow here (can be whole flow or part of your flow e.g. download flow or just an activity e.g. readStatusBar)
It seems that you have trouble getting an answer to your question in the first 24 hours.
Let us give you a few hints and helpful links.
First, make sure you browsed through our Forum FAQ Beginner’s Guide. It will teach you what should be included in your topic.
You can check out some of our resources directly, see below:
Always search first. It is the best way to quickly find your answer. Check out the icon for that.
Clicking the options button will let you set more specific topic search filters, i.e. only the ones with a solution.
Topic that contains most common solutions with example project files can be found here.
Read our official documentation where you can find a lot of information and instructions about each of our products:
Meet us and our users on our Community Slack and ask your question there.
Hopefully this will let you easily find the solution/information you need. Once you have it, we would be happy if you could share your findings here and mark it as a solution. This will help other users find it in the future.
Thank you for helping us build our UiPath Community!
UiPath project settings now has an option to enforce HARD timeout,
if this is set to TRUE, it means if SAP Hangs for whatever reason e.g. popup , the workflow should stop and throw an error after the timeout