We've run into a curious problem with file event-triggers in VisualCron.

Here's what happened:

We created a test job that watched for a file to be created on a networked server. When it saw the file it wrote to a different location and then deleted the file. We had some difficulty with permissions that resulted in frequent erroring that we ultimately resolved. Once they were resolved we deactivated the trigger on the test job.

A few days later we created the actual job that will run when triggered, but when we went in to test we found that the watch file was being almost immediately deleted still. We went into the test job, verified the trigger was inactive, then proceeded to inactive the tasks in the job, and ultimately tried deleting the job only to find that it that the trigger and the originally assigned tasks (which no longer exist in visualcron) were still firing.

We eventually killed it by revoking permissions on the folder until it eventually errored out (which it did report to visualcron in the log as attached to unknown jobs and tasks).

Has anyone else run into this or this kind of behavior before?

Which version are you running?

We have seen it happen in an older version. We would be happy to know how this can be reproduced. One thing we plan to add is a window where you can see all Active Triggers which might also help in this specific case.

---

We are running in an older version: 6.1.5.

If upgrading is the fix that's fine, I just couldn't find any proper documentation so I wasn't sure that was the case and it was a known problem.

Maybe this will help me pound the table to expedite the upgrade!

Yes, that version is almost 4 years old. Please upgrade and let us know!

---