When I use ChromeQuit and reference a Chrome Session ID that does not exist, it crashes the compiled macro scheduler process.
On infrequent but persistent occasions, I find that chromedriver will not launch a new session until I logoff and sometimes not until I reboot.
I suspect that if I were to gracefully end chromedriver sessions instead of using
Code: Select all
KillProcess>chrome.exe
KillProcess>chromedriver.exe
If there were commands like these, I could check whether I need to shutdown a session or not.
IfChromeSessionExists>session_id
ChromeSessionState>
ChromeSessionStatus>
ChromeSessionInfo>
For now, I am avoiding ChromeQuit in my scripts, because of the hard crash and popup windows that appear if I call it in an error handling routine.