I have noticed twice since switching to COM the monitor allows the application to unload. The site is checked every 10 minutes. Once unloaded the monitor is not able to re-load the servers automaticlly but clicking on the "Check Site Now" button does awake the site.

THe monitor is configured to visit my root URL without any page reference (https://www.MyDomain.com). The text the monitor is searching for within the page comes from my user login page which by design is an Angular Route redirect that occurs after testing to see if the user is logged into the system.

This configuration works correctly for many hours at a time and why the servers are unloading in the first place is puzzling. But just as much of a mystery to me is why the monitor on repeated hits does not cause the COM to reload.

At this point I need to manually unload the servers and wait for the monitor to cycle around to testing and see if there is a way to cause the failure to occur. Maybe the problem is the way the servers are unloading and there is a difference between manual unload and inactivity unload. Or what if the monitor hits the unloaded site and does not wait long enough for a reply while the servers are loading up and somehow it or IIS caches the doamin page without the angular redirect so from this point on it continues to fail... and the manual check site now forces the monitor to ask for an un-cached page.

No clue but it would be nice to know how to fix the problem.

You should point the monitor at a direct Web Connection link not some redirection link. Create a method called ServerPing or something like that and call that directly from the monitor to avoid any sort of weird re-routing logic. My guess is you're hitting a routing issue where re-write is not actually hitting your backend but just hitting static HTML so nothing reloads.

+++ Rick ---