I am seeing a problem after I restart HS3. I run quite a few scripts via events. If HS3 is offline for 10 minutes and I have events that are normally suppose to run every minute, all unrun events will execute at the same time when HS3 restarts. So if there are many events that normally run every minute, I could see 50-100 events triggering all running a script and will begin to get error messages that too many scripts are running at one time. Of course this hammers the CPU time. If I wait, eventually the unrun events will complete and the schedule will settle into its normal schedule. If HS3 is offline for 30 minutes, the number of events that kick-off simultaneously when HS3 restarts is easily in the hundreds.
Is there some setup setting that I need to uncheck (or check) to tell HS3 not to try to run events that did not run when HS3 was offline? Is there some option in each event that I need to check (or uncheck) to tell HS3 not to try to run events that did not run when HS3 was offline? Is anyone else seeing this problem?
HS3 3.0.0.258. (this was doing this when I was running 3.0.0.208 as well.)
-Cliff
Is there some setup setting that I need to uncheck (or check) to tell HS3 not to try to run events that did not run when HS3 was offline? Is there some option in each event that I need to check (or uncheck) to tell HS3 not to try to run events that did not run when HS3 was offline? Is anyone else seeing this problem?
HS3 3.0.0.258. (this was doing this when I was running 3.0.0.208 as well.)
-Cliff