I have a job with a file trigger pointing to a UNC path and using polling. Ordinarily, the job works fine (trigger is on 'Created' with notify filter of 'File Name').

However, this morning the job failed for a legitimate reason. I resolved the problem and re-dropped the same file into the folder the trigger monitors. No matter what I tried, the trigger did not fire until I put another file in the folder with a different name.

Is this by design or a bug? How do I get the trigger to fire following a failure?

Regards
Neill

You should not use "polling" option unless you are watching a Samba folder. The polling option will give you a delay which may result in what you experience.

---

The delay was not due to the polling delay. It's currently set to poll every minute and I gave the job at least 5 minutes before assuming the trigger wasn't going to fire each time I investigated the problem.

When things run smoothly, I can drop a file into the network share, wait (for up to one minute) and the job will trigger and complete successfully. However, following a bad change to task sequencing, the job failed. I resolved the sequencing problem, moved the file that triggered the job to a temp folder then moved it back into the monitored folder. The trigger never fired. Without any changes, I then copied a differently named file into the monitored folder and the trigger fired (within a minute).

Regarding the use of only polling Samba folders - I believe non-polling file triggers can be unreliable when pointing to network drives, i.e. network interruptions can stop the trigger firing. Polling allows retries on error etc and therefore provides more resilience. For this reason, I'm happy to take the hit of a minor delay before the trigger fires.

Neill

As you have confirmed that it is not a Samba folder I see no reason at all to use the polling variant.

The polling variant:

* cpu intense
* slower reaction
* more prone to errors

There are only disadvantages with the polling alternative which is really a workaround instead of using the built in functions in Windows.

Polling Triggers, just as normal Triggers can fail due to network access as well.

You can work around disruptions in network by increasing retry values.

---

Ok, I'll de-selct polling and see if I can recreate the problem

Thanks
Neill

I can't reproduce the issue with polling disabled. I'll keep it disabled and see how it goes.

Thanks
Neill