b37119af-03ba-437b-b612-b0cf064c18d6.zip

Some activities such as **SAP.ReadStatusbar** activity do not follow the Timeout property if the SAP session has hung or has been disconnected.  It will keep running forever until the user manually kills SAP.

  

With this snippet, you can enforce a timeout by having a separate timeout handler that runs independent of your main flow, meaning it will not get affected by events such as SAP being busy/hung. If the timeout does occur you can let the robot perform actions such as kill SAP etc, which will solve the above problem.

SAP Timeout handler for activities that will become stuck if SAP has hung or gotten disconnected.

7f0832c6-5cbc-4716-aa20-418396cfb4c6.png

MIT License Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the 'Software'), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED 'AS IS', WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

SAP Timeout Handler