Is there a set time that one whenever event will slow down the script. I have not used whenever events yet and in training was told to try to stay clear of them. I'm not sure if it was because of a problem with them or they just slow down the process too much. During the training they pushed the fact that you should know what the process is and you will not need the whenever if you understand the application. Instead use the OnError.
I now have a timeout in the application and if you do not use the application it will log you out but does not tell you until your try to use the application and this is a good place to use the whenever event. If you see the UserName and Password boxes after your first click or action, then run the login event and start the script over.
Well, i don't agree with what you've been told on your training. I have been using a Whenever event to monitor run time errors in my target application. It works very well for me and i don't see that causing any performance issues.
My implementation of whenever fits my framework and script development conventions.
Your situation sounds good for implementing a whenever event. I would suggest you give it a try and decide whether this is what you need.
If you always do what you've always done, you will always get what you've always got!
Thanks for the reply flaggmann.
I will look into this. My concern is returning control to a different place as I will need to reload the page that did not load because the user was logged out by the system. I have some research to do on this whenever topic.