Henrik,
It started after I upgraded to 6.1.1. It originally only happened with 1 job but last night that number increased to 3. It correctly executes all the tasks from the initial trigger, but it immediately starts running the first task again, since my first task is to copy the trigger file to a temporary location, it errors out because it can't find the trigger file. I've made no changes to any of those jobs in several months. I originally created the jobs in 6.0.9 and upgraded to 6.1.1 about 3 weeks ago. This problem never happened in 6.0.8.
I'm starting to catch alot of flak about this. This issue is starting to catch our Bureau Chief's attention. Please give us some feedback on whether it's being looked at and any workarounds or potential solutions.

First, to help debug this, I would appreciate if you could upgrade to 6.1.2. This would give us the same testing base to compare with.

Then, turn on "Extended debugging" in server settings->log. Next time it happens, please send us log_serverDATE.txt to support@visualcron.com

---

Thank you. Will do.

I upgraded our test box to 6.1.2. I was unable to recreate the error from the production box running 6.1.1.
I did notice that the up time in our production box was close to a month. I went ahead and rebooted it this morning. So far, 2 jobs that were giving me the error yesterday have worked correctly today. I have 2 more jobs that will run this evening that were flaking out yesterday that I will keep an eye on.

Thanks for the feedback - please let us know.

---

The reboot of the production box seems to have fixed the double-firing of the jobs. After the reboot, the error has no repeated itself.