Hi support,

We're running multiple VCRON servers in different systems. (developer machines and also VM servers).
After developing and testing the jobs, the jobs are 'cloned' or 'copy.pasted' or via 'export and import' placed to the other servers.
Running this jobs on the new servers works fine, but there is stange habbit on it.
It seems that the VCRON client does not know the executing server anymore.
All clients reporting a running job if this 'cloned job' is running on 1 server.
example:

-create job1 on server A
-clone this job1 to server B

- running job1 on server A with client on server A: start fine
- at the same time in the client on sever B reports : job1 = running on server B.
--> but it isn't.

What do we wrong? or what's goiing on in the VCRON clients ?
Because we're using more and more servers and jobs, it becommes impossible to track the batch-flows.

Thanks in advansed for your help.

I am not sure I follow you or can reproduce.

1. with one client I am connected to Server A and Server B
2. I create a Job on Server A
3. I copy that Job to Server B
4. I run Job on Server A - success
6. I run Job on Server B - sucesss

What am I doing wrong?

---

after the copy, run only the job on server A, be shure it runs long anough.
while this job is running, connect the client to server B. At that time, the same job on server is reported as 'running', but it's only running on server A.

I cannot reproduce this, please let me know if this are correct steps:

1. with one client I am connected to Server A and Server B
2. I create a Job on Server A
3. I copy that Job to Server B
4. I start long running job on Server A
5. I connect to Server B
6. Job is only running on Server A (as it should)

---

I can't explain, and it also not always.
I retest this right know and did not get the same problem.
I got something else: see attachment.
Maybe this leads to the real problem.

-> job is still running, but status is different between the client and the report 'running jobs' on the server.

I can't explain, and it also not always.
I retest this right know and did not get the same problem.
I got something else: see attachment.
Maybe this leads to the real problem.

-> job is still running, but status is different between the client and the report 'running jobs' on the server.

Is it really running? Did it not stop running after the second last Task failed?

---

I've restarted the client. Statusses are the same now.
This is a difficult situation. If we can not be sure the status on the client reflects the status of the job on the server, it's difficult to manage.
I saw in the forum more people have a problem likewise. I followed one possible solution and extracted all job, and imports it again. Maybe this solves it for the moment.

I've restarted the client. Statusses are the same now.
This is a difficult situation. If we can not be sure the status on the client reflects the status of the job on the server, it's difficult to manage.
I saw in the forum more people have a problem likewise. I followed one possible solution and extracted all job, and imports it again. Maybe this solves it for the moment.

Reimport is no solution to the problem. We are still awaiting feedback from another user regarding something similar (but not the same).

My question in last post were if you really was expecting the Job to be running? According to your screenshot the Job failed at the second last step. But running jobs window showed that it was still running. It is important for us to know where the problem is. If it really was running at the moment or that the Client just had'nt removed it from running jobs window?

---

ok.
Job has failed, and stopped.
In this case, the 'running jobs' window was incorrect.