Hi,

We have version 8.5.0 on server 2016.

We have many jobs and I would like to be able to check if some jobs are running longer than a defined time or if a job has been set inactive etc.
There are many things that can go wrong and it should be possible to do some health checks of VisualCron and the jobs.
E.g. it should be possible to iterate through the jobs and do some checks.
How is that possible, please?

Vi have downloaded the latest version and it appears very unstable, like leaving the jobs running even if the process has been completed.
It happens on and off, so we need to be able to add some jobs to check that the jobs are still very much alive.

Thanks.

First I recommend that you upgrade to 8.5.1. to at least start the debugging more of the job running status. I also think we should continue that discussion separately on email so we can attach log files easier. Please use support@visualcron.com for that.

About running longer than you can create a Default behavior in Server settings->If running longer than->Send Notification for example.

---

Thanks Henrik,

I am trying to find ways to automatically check if everything works as expected.
It's not a debugging question, so no need of sending log files.
One way could be to build some general rules, as you pointed out.
One thing still missing though, is to build compliance jobs - jobs to prove that the system are compliant -> have done what it is set out to do.

thanks.
Peter

Thanks Henrik,
One thing still missing though, is to build compliance jobs - jobs to prove that the system are compliant -> have done what it is set out to do.

It sounds like you need something custom. Maybe using the API will get you exactly what you need. This could then be used in .NET Code Task or Task repository to provide some kind of result.

---

Well, I have tried to download the sample project of yours, but unfortunately I could not get it to work (would not compile - too many unknown dependencies).
I haven't gone deeper into why.

Well, I have tried to download the sample project of yours, but unfortunately I could not get it to work (would not compile - too many unknown dependencies).
I haven't gone deeper into why.

Maybe you have another .NET developer in-house. We are happy to help if you get stuck.

---