I seem to be having an issue with stopping jobs/tasks.

Basically, if I try to stop a job or task that's part way through, the job/tasks still shows as running. I can't see a refresh button and closing and opening VC does nothing.

The only way to stop it is to stop the service - somewhat inconveinent.

Any ideas?

Sometimes I have this behaviour as well, and indeed the only way is to restart the service.
I normally encounter them when I'm heavily testing jobs.

Do you have any specials on the particular job, like timeouts, on error conditions or so?
:-s

Regards
Erik

---

It depends on the Task type - how we stop it. For example, Execute Task is stopped immidiately. FTP Task may take longer as it will be waiting for last transfer or request to done.

---

Yes, we have timeouts, conditions etc.

However, even if it has a timeout, if I stop it - I want it to stop. Some of my timeouts are 10 hrs plus, some of my conditions are looped for the same.

The problem are the Conditions. Because it is possible to create infinite loops there. We'll see what we can do here. What kind of flow do you have? Is the Condition starting another Job, restarting the Job, another Task or?

---

It doesn't appear to be just jobs with timeouts/conditions but all jobs.

They all still show up as running.

An example of a condition would be to look for a set of files, retry every 30 mins for 3 hours, if they are not there, then run a ping task which notifies us of failure.
If it finds the files, it runs the task associated with it.

If you have any other Tasks (that does not have any Conditions and that you can't stop) then please let us know which Task types that cannot be stopped.

---

We have done some modifications for the Conditions so you will easier be able to stop the Job. The changes will be published in the next beta.

---

Hi,
I have experienced this issue since I started using version 4.x a year ago and now I am at version 5.1.0 and it is still present. I have never been able to stop at Job when the condition was not met. Most of my conditions stop in 30 minutes but it would be nice if Stop at the Job or Task level meant immediate stop. It is problematic having to always stop the service to end a Job/Task.

Has the FIX to make this stop sooner actually been implemented?

Thanks,
Noel

How is your Condition loop constructed (what kind of wait interval do you have)?

Hi,
I have experienced this issue since I started using version 4.x a year ago and now I am at version 5.1.0 and it is still present. I have never been able to stop at Job when the condition was not met. Most of my conditions stop in 30 minutes but it would be nice if Stop at the Job or Task level meant immediate stop. It is problematic having to always stop the service to end a Job/Task.

Has the FIX to make this stop sooner actually been implemented?

Thanks,
Noel

---

Hi,
All my conditions are configured at the Job level and check to see if file(s) exist prior to running the defined tasks. Most of the Jobs are configured with a timeout of 35 minutes (maximum configured at 1.5 hours) and I have "Consider timeout as error" checked so I get a failure email. (Note: the timeout time period configured at the Job level, the condition check and the conditions action rules shown below, always work as expected)

My actual conditions are one or more file checks and they have these settings:
On Match All
continue
On Match Any
retry (2 Minutes)
On Match None
retry (2 Minutes, 59 seconds)
On Match Error
exit

Besides never being able to successfully for a Job to stop when the condition isnt met I have never been able stop a running task that has hung up for some reason. I have experienced this with email and FTP tasks.

Thanks,

Noel