I have some jobs than monitor a certain exchange email box. Sometimes, these jobs just shut off. VC says "no active trigger". Nothing in the log that I can see that indicates why, no recent errors.

So, these jobs just quietly die sometimes, for no known reason. There's more than one job that monitors the same box, and they don't die together. No pattern that i can see. I just have to open the job and click the trigger to get them working again.

I tried creating a job to monitor when other jobs' triggers go inactive, so at least I can know there's a problem. But I can't get that to work. Is there a way to do that?

Thanks!

Dear all

Have the same issue, the job that monitors the triggers is not working correctly. I remember that I read once something about it (couldn't find the thread anymore 😕 ), but I have never seen a post or something in the change log that it is solved now.

Is there a plan to solve this?

We have a lot of file monitor triggers and if they go inactive (without giving an information) we run into problems. Just found 10 jobs today where it occured.

Thanks for the feedback

Susanna

I don't know why this post was not answered in the first place.

Anyway, there are many parameters and error reasons.

First to check is the connection timeout and retry values. If network is down for any reason these settings matter in order to reconnect.

---

On a side note.. any hopes of getting an unlimited reconnect feature/option?

I don't know why this post was not answered in the first place.

Anyway, there are many parameters and error reasons.

First to check is the connection timeout and retry values. If network is down for any reason these settings matter in order to reconnect.

Might be something. The main reason why we did not do that is that this ensured some control.

---

Hi Henrik

Thanks for the info... But it didn't answer my question ;o)

Is there a plan to solve the issue of the trigger monitoring that is not working correctly?! My job checking if a trigger deactivates never fires...

Thanks

Susanna

Hi Henrik

Thanks for the info... But it didn't answer my question ;o)

Is there a plan to solve the issue of the trigger monitoring that is not working correctly?! My job checking if a trigger deactivates never fires...

Thanks

Susanna

1. which version are you running now?
2. what happens if you disable the local network on the computer - does it fire then?

---

Thanks.. just something to look into as it is no fun when exchange or network does go offline for 6 hours and then you have to click on 20 or so jobs to activate them back up!

Might be something. The main reason why we did not do that is that this ensured some control.

Hi Henrik

We run version 5.6.9 of VisualCron.

I did a test yesterday with a trigger, checking a folder on my computer. During the night my computer is switched off - so for sure the trigger will be activated and the job that checks the trigger should fire (and send an email with a message to me).

This morning I didn't receive an email and when I checked the VisualCron I received the attached error message... I've never seen a message like this before on a server, where VC is installed. But even after I clicked ok, the job monitoring the trigger deactivating did not fire. The setting of the job is monitor "trigger expires (inactivate)" and it's going to send an email to me.

Thanks a lot for your help

Susanna

Hi Henrik

We run version 5.6.9 of VisualCron.

I did a test yesterday with a trigger, checking a folder on my computer. During the night my computer is switched off - so for sure the trigger will be activated and the job that checks the trigger should fire (and send an email with a message to me).

This morning I didn't receive an email and when I checked the VisualCron I received the attached error message... I've never seen a message like this before on a server, where VC is installed. But even after I clicked ok, the job monitoring the trigger deactivating did not fire. The setting of the job is monitor "trigger expires (inactivate)" and it's going to send an email to me.

Thanks a lot for your help

Susanna

When this message is showed it is currently "too late" and the Trigger is now deactivated. The Trigger have given up checking (with all its retry settings) and is now telling you what happened. Clicking Ok here does not produce any results. Maybe we should add an option to activate the Trigger again.

How long was the server down and what retry settings do you have?

---

Hi Henrik

Sorry for the late reply - was a little bit too busy the last week...

My computer was down over the night - and the retry is about three times and the interval is 5 seconds.

Although I received the popup message on the test-server I've never seen this before on the live server... And as said, my "trigger expires" never fired, not on the test server with the message - and not on the live-server where no message ever appeared.

As I'm not connected every day to the live server to check it would be more helpful, if my job, checking if a trigger expires would fire - it will send me an email then. With a popup message on the screen I have to monitor the server all the time.

Anyway, IF a message appears it would be helpful, if it would be possible to reactivate the job... ;o)

Susanna