Hi,

Whilst we have had very good experiences with triggers on local drives and *some* / native windows shares we are having persistent issues on others.

For example triggers on our NAS (Hitachi - Tier 2 Disk) are not reliable and we have either had to resort to high frequency jobs rather than triggers, or moving these operations onto standard windows shares.

The provided 'Use polling (Samba compatible) check box isn't applicable / doesn't seem to be helping us.

We are not experiencing these issues in VisualCron using the shares on the Hitachi NAS performing VisualCron Tasks:
- File List
- File Read
- File Rename
- File Copy / Move
- File Delete

Or in Windows in general (when using or mapping the drives).

These are not / do not fit the remote trigger model (FTP), and the current File Trigger model is not stable for us on these shares.

We need some sort of control over trigger polling / trigger logging / alternative trigger setup like a File list, that might be able to be specified to poll every 5 minutes for example, but only fire if a file meets the criteria (as with present triggers).

Even if this was higher cost / overhead, as long as it was much more tolerant / compatible and a polling frequency was able to be set that would do the job.

Whilst this can be achieved in VisualCron by a file list, conditions, and high job frequency, a trigger is a much better solution from a noise perspecive. High Frequency jobs are not a desirable solution, from a server load, or server logging perspective / Client Message.

Update:

As of 7.0.5 Beta (Probably the 7.0.3 Remote File Trigger changes with Credentials) initial testing with Polling on with our NAS has been successful.

See attached

Without 'Polling on' triggers on the NAS appear unstable / does not fire / fails with the error attached (but we don't experience any other issues using the NAS in visualcron).