Hi

Seems to be such a simple thing but can't get this working!

I have a requirement to start a series of console applications every morning (these are batch routines that run in a console, and also GUI applications). Plan is to have a single scheduled job, with a number of Execute tasks - 1 for each console application!

I call the .exe's in the 'Execute' task, but as soon as they start, the Execute task should end and move on to the next Execute task. However, when the exe starts, the Execute task stays active with 'Status' at Running - up to 99%, and stays there.

I've tried executing a '.cmd' file that 'Starts' the .exe but the same thing happens!

As these are console applications they have to run in the Foreground with desktop credentials as we have no way otherwise of monitoring processing.

I am running V8.2.2 - Am I missing something obvious here?

Cheers

Andy

Even though it might be not related. Please upgrade to 8.2.3 as we fixed a Variable issue here which could cause irregular behavior.

First thing you should verify is that Foreground Task works and connects fine by using full path to notepad.exe in Command. Does it work?

---

setting the exe as C:\windows\system32\notepad.exe and run in Foreground (Execute on any desktop session) does exactly the same thing. Starts Notepad, but then the Execute Task stays running at 99%

Yes, this is normal as long as it (notepad.exe) is running.

---

So the Execute task can't just run an exe (or shortcut) and exit, leaving that task running? Could we expect any resource overhead if, say there were 20 or 30 of these tasks running?

You can fork in batch file:

http://stackoverflow.com...rk-in-windows-batch-file 

---

Okay thanks Henrik - that might be an option. I will monitor the resource overheads and if it gets noticeable we will look at an alternative solution

Cheers

Andy