I have a couple of processes using the Word and Excel Application Scope. I have noticed that sometimes when the process is run (from a VM triggered by Orchestrator) it seems to freeze after doing the actions with a Word/Excel application scope. From the logs I can see nothing happens for hours and the job needs to be killed as the stop action is not sufficient.
In a specific process I am using the Word application scope to convert a Word document to PDF and after that nothing happens. I have then implemented a delay of 5 secs and then killing all winword processes. In the log I can see that the Word process was killed for the first two instances but for the rest of the PDF conversion it ran through without killing the Word process.
To me it seems that the job is waiting for Word to close when the activities in the Word application scope is performed before it can continue. Otherwise I do not understand why it can wait for hours without doing nothing - but somehow it must still be running since the kill action is performed?
Any suggestions or ideas?