I see the support case. The support person has not forwarded to me yet. What I need and don't see in the attachments are log files which represent the hanging. I need to get some bead on where the hang tends to occur.
Also, your description infers that the issue is with newly created TDP 4.1 scripts. I don't suspect the scripts themselves, rather TDP 4.1 that is running the scripts. It is possible to have an older version of TDP run the newer scripts as long as they don't use newly introduced features of automation, which there weren't any in 4.1 If you want to try this, go to the task scheduler in TDP 3.8 and press the "migrate" button. See attached. This will take selected scheduled activities and run this with the version of TDP you reset them with.
This will not help debug things but might keep any production scripts more stable. I would still get a script that often hangs and put on verbose logging. When it hangs get a copy of the automation script and give to support. By default this files are in path below (just edit to your profile name)
You could also run a script daily to zip up all the files in the directory and email to you. Then you have the log files when something hangs.
C:\Users\dpeabody\AppData\Roaming\Quest Software\Toad Data Point 4.1\Automation
