What I miss in the current version is using variables in a 'file trigger' folder path.

Whe have a folder in which subfolders are created every day with date names. I want to trigger on files in the last created folder (current date) on a daily basis.


[edit info]My question was wrong, now it is ok 😇 .[/edit info]

---

Please try this version which refreshes File Trigger values at Interval value (default 60 s).

http://www.visualcron.us/download/VisualCron4.exe  (4.9.3)

---

I created a job with a file trigger (default settings), and the filepath is: F:\{DATEFORMAT(mm)}\ and file mask is *.*.
I changed the polling interval to 15 seconds.

So it should look at directories with a number corresponding to the minutes amount.

The time is 11:33. I had a dir called: f:\33\. I copied a text file in this folder.
Result: trigger didn't go off. 🤔

Without the variable in the path (direclty in the root) the trigger will go off if i put the file in there, but this is standard behaviour.

If I put the variable in the filename, than it is working. The file mask is now {DATEFORMAT(mm)}.*
I used filenames with a name corresponding to the minutes of the current time. =d>

Is it possible, because the of the polling interval, to have the path looks at the variables as well? [-o<

---

We can't reproduce this.

Only thing I can think is that:

* folder was not created when the trigger was added which caused the trigger to fail (please check the logs for failures)
* you moved the file to early (before 15 seconds had moved and switched to that directory)

---

The answer to this is that indeed the folder isn't there when I created the trigger. That's why I use a variable for it.
at some day / some time the variable will match a newly created folder and in there he should trigger on files.

Is this how you see it, or do I see it wrong? 🤨

---

The problem is that if the folder does not exist the file trigger will return an error and try to reconnect. After some time, when reconnect has failed a couple of times it (the trigger) will be deactivated.

I understand the problem with this in your situation but the trigger must be active to find a certain folder or file. At the same time it can't exist "forever" and must react to errors and timeouts.

---

So you're saying if the trigger is made the folder should be there?

I looked at the log file and there is indeed a line telling me the trigger cannot be added due to an invalid directory name.
In the cliet I cannot see that the trigger is inactive. The checkbox is still checked telling me it is active.

There is an option 'on error reconnect attempts' and 'on error reconnect interval'. Shouldn't these settings de used for the inactivate trigger?

So, if the trigger is inactive, the only way to activate it again is a manual task?

---

The first time you add it does not try to reconnect. The reason for that is that you should now directly if it worked or not.

Yes, you have to activate it manually after that.

---

The reason for that is that you should now directly if it worked or not.

You ment I can see this directly? I had to open the log file for it to see that the trigger was not activated.
No direct GUI message was shown to me.

==

We might be at different tracks here, but you are telling me that the variables in the directory can only be used if the directories you want to match with are allready in place?

---

Yes, directories has to be in place from the beginning - at least the start watching directory.

I thought we showed a messagebox if trigger could not be added but that seems to have "fallen away". I will add to the to do list that we show, more clearer, if it has failed.

---

The messagebox is now added for the next version. If it should fail the first time.

---

ok! Nice to have feedback if something is not working 😉

---