Hi Randall, Stu, and WeatherCat fans,
For this to work better for me I rearranged on which one shut down first for me
. . . . . .
Well, that depends on if you have
WC Web Data Uploader and
WC Twitter Uploader sending requests to
WC Status Growler to see if the Internet is up or not. If you do, then there is always a chance either one will restart
WC Status Growler before you have shut them down. The same point applies to
WC AppleScript Tags Processor.
Now it is true, the longer the delays in the shutdown process, the longer the interval when an AppleScript might make requests to one another or WeatherCat. Now that you mention this, I think I should knock these values way down. Even 1/2 a second is plenty of time and the AppleScript delay command accepts decimals.
Even so, it is still
"more better" to have
Stop WeatherCat Scripts also shutdown WeatherCat instead of using the WeatherCat shutdown action when using my AppleScripts. Even if the odds can be made very small, there is always a risk that something will be restarted if you don't shut things down in the right order. If you really want to have a bullet-proof sequence, you have to eliminate any such chance. It doesn't matter too much I suppose if you restart things "by hand," but if you want to completely automate a restart process say while your sleeping - you don't want a surprise waiting for you when you check your computer in the morning!!

Cheers, Edouard
![Cheers [cheers1]](https://athena.trixology.com/Smileys/default/food-smiley-004.gif)
P.S. On second thought, the situation is even more complicated. Even if the shutdown sequence will work perfectly well, there is a possibility of the processing taking a very long time. The two scripts that upload data to the Internet won't quit in the middle up uploading. AppleScript isn't smart enough to interrupt the idle handler an AppleScript is "told" to quit. If there is a request to an upload service and the server is very slow to respond - both
WC Web Data Uploader and
WC Twitter Uploader could take as long as a minute to quit. Fortunately, AppleScript doesn't do the next step in the script until the previous one is completed. So
Stop WeatherCat Scripts will patiently wait for each script in turn to quit before telling the next one to do to so. Nonetheless, it is possible for this process to take as much as several minutes when your Internet connectivity is poor.
P.P.S. On third thought (why am I thinking so much!

) I should remove all the delays in
Stop WeatherCat Scripts. The way AppleScript processes each line guarantees that nothing will be left incomplete as the shutdown sequence unfolds. The delays are only need for
Start WeatherCat Scripts to avoid having
WC AppleScript Tags Processor getting requests for all the other AppleScripts at once.