I have a simple Job that triggers when a file is created in a folder. When the job has triggered, it is set to inactivate (the Run Once job setting).

Lately, I've noticed that this job is failing almost daily. Looking at the Job log, the job is triggering 2 times at the exact same time (see attached file "VC_TriggerMultiFire.png"). One instance works properly/succeeds. The other fails as the process is already running. I have also attached a screenshot of the trigger settings for the job for reference.

I cannot figure out why the job is triggering multiple times instantaneously. Any thoughts on what might be occurring and how to ensure it doesn't continue happening?

I goofed on the first attached screenshot. The Move File process is irrelevant, though it would appear to be the cause of the issue. It's not. Simply a copy/paste error.

Could you double check which kind of Triggers you use in both of the Jobs?

The reason for failing is probably something else - double click on the output to see why.

---

The Trigger is a File Trigger that fires when the file is created.

jt, I was experiencing the same problems as you. I have 4 jobs firing off twice, simultaneously. The second time around, they were erroring out because I remove the file after I finish processing it.
The up time of our production server running Windows Server 2012 was close to a month. I rebooted it and so far, 2 of the 4 jobs are behaving.

Please upgrade to 6.1.2 and let us know if it does not resolve it.

---

We are experiencing the same problem with jobs firing multiple times when a file is created in the folder. This causes the job to error.

We are on version 6.1.2 (Build 41147)

We are experiencing the same problem with jobs firing multiple times when a file is created in the folder. This causes the job to error.

We are on version 6.1.2 (Build 41147)

Please attach a screenshot of the Trigger settings.

---

I may need to clarify what processes are occurring...
My triggers are watching a folder where files are dropped. The job should fire on the first time the file is CREATED.

The watched-for files may get updated & overwritten throughout the day; however, based on the trigger definition (file is created), it should not fire again.

However, it appears to be firing every time the file is updated (which is not what I want). Attached are screenshots of my trigger settings.

I may need to clarify what processes are occurring...
My triggers are watching a folder where files are dropped. The job should fire on the first time the file is CREATED.

The watched-for files may get updated & overwritten throughout the day; however, based on the trigger definition (file is created), it should not fire again.

However, it appears to be firing every time the file is updated (which is not what I want). Attached are screenshots of my trigger settings.

It sounds really strange as we cannot see any big changes here in a while. It would be interesting to know if the Trigger really fires twice or if it is just the Job that runs twice. Could you turn on extended debugging and then send us the log including Job name and time to support@visualcron.com

Also, are you using the Put Job in queue option?

Are you also using 6.1.2?

---

A quick response:
- I am using 6.1.2
- No, it is not in the Job Queue...I want it to import once. I have conditions set up that require it to wait for other processes to run first before running.

We are experiencing the same problem with jobs firing multiple times when a file is created in the folder. This causes the job to error.

We are on version 6.1.2 (Build 41147)

Please attach a screenshot of the Trigger settings.

Could you turn on extended debugging and then send us the log including Job name and time to support@visualcron.com

---

Thank you all for the feedback so far. What we can see from the logs is that the system fire the Created events many times. The question is why. Is it possible for you do do the following test:

1. deactivate all Jobs
2. restart the VisualCron service
3. activate one Job only (with a File trigger)
4. place a file there - does it Trigger once or many times?

If it only Triggers once then activate another Job with file Trigger. Repeat procedure - same result?

---

Thank you all for the feedback so far. What we can see from the logs is that the system fire the Created events many times. The question is why. Is it possible for you do do the following test:

1. deactivate all Jobs
2. restart the VisualCron service
3. activate one Job only (with a File trigger)
4. place a file there - does it Trigger once or many times?

If it only Triggers once then activate another Job with file Trigger. Repeat procedure - same result?

After deactivating all jobs, restarting the service, and activating a test job, I was able to successfully trigger the job 1 time.
After re-activating and testing again, I got the file to trigger once, as desired.

However, after the initial test, I ran the process again as it would on a normal day.
The trigger is watching for a file to be created within a specific folder. The job runs once, then deactivates. The original trigger file remains in place in the original folder that triggers the job. However, that file gets updated 2-3 times a day and gets a newer date/time stamp. From what I can tell, this does NOT trigger the job again (as the trigger is a FILE CREATE trigger). But when I drop the file in there as a new file (delete the existing, re-drop the file to trip the trigger), the job will run 2-3 times and error. Odd? Yes. Confusing? Absolutely!

I attached a screenshot of the Job Log that shows the job triggering 2-3 times instantaneously and failing. The log entry where it succeeded is after the test from above.

Please try this version:

http://www.visualcron.co....aspx?g=posts&t=2575 

We found that there was a problem in deactivating Trigger when using Run once option.

---

I upgraded to version 6.1.3 and tested my triggers over the past few days. It appears that this version DOES fix the multiple triggering issue I was seeing with previous 6.1.x versions. Thanks so much! I can now recover my sanity.

I upgraded to version 6.1.3 and tested my triggers over the past few days. It appears that this version DOES fix the multiple triggering issue I was seeing with previous 6.1.x versions. Thanks so much! I can now recover my sanity.

Thanks for the feedback and patience regarding this.

---

Hi all,

please update to this version and turn on Extended debugging in Server tab->Log.

http://www.visualcron.co....aspx?g=posts&t=2575 

Hopefully it will help us finding the cause.

If it happens again please send log_serverDATE.txt to support@visualcron.com

This does not concern the issue jtnelso had as that is another issue that is fixed.

---