Hi Support

Not sure what can be followed up with this one so just hopefuly that there is perhaps a possible explanation?

We have a job that triggers when a trigger file is dropped in to a trigger folder. The Trigger was active yet the job wouldn't trigger. Tried moving the trigger file in a few times but no luck. Disabled the File Trigger in the job, then re-enabled it and everything ran fine. Same trigger file, so nothing was different.

Checked the Server Log file and there is not a single entry until the job ran properly, so I'm afraid there isn't a lot to go on here.

Are there any circumstances in VC V 6.1.8 build 16372 that might cause a trigger to act as if it is inactive when it is ticked (active)?

Cheers

Andy

Hi Andy,

we have not seen that. Please confirm that you only use Created+Filename. Also, when testing you should "copy" and not "move".

Third, before any testing it is recommended that you turn on Extended debugging in Server settings so that everything is logged.

---

Hi Henrik

The Trigger is defined as 'Created' and yes, for testing, we copy the file trigger in to the trigger folder so we can easily test the job if needed.

Extended Debugging is switched on but again, there were no messages at all when a trigger file was copied in. It was almost as if the Trigger wasn't set even though the activate box was ticked.

It is a strange one and it is worse that it can't be recreated. I guess it is just a case of waiting and hoping that the trigger doesn't fail again.

To be honest, this is the first time I have seen anything like this so will put it down to a one-off glitch.

Cheers

Andy

We had another user experiencing similar problem some days ago. As this behavior is not normal I am thinking of external problem like a Windows update or similar.

---