So, we have a couple of jobs set up on our VC server. They work well 99% of the time. Unfortunately, something goes wrong once in a while. The jobs are set up like this.

Step 1) An FTP task on an interval trigger downloads files from an FTP server and places them in directories on the local machine. (According to FTP logs on the server, this is happening without any issue.)

Step 2) A file trigger watches for new files in four specific directories. (This is set up in four individual jobs, one for each folder.)

Step 3) When one of the file triggers fire, the document (.pdf) is sent to a specified printer.

Step 4) After the print, the file is moved into an archive folder for the current day.

The problem is, I can't seem to determine where the process is breaking down. The file is definitely being downloaded. Sometimes the file does not get printed. Under version 5.6.2, the file would sit in the directory and nothing would happen with it. To attempt to correct this, I upgraded everybody to 5.6.9, which was running in one of our locations and the operator indicated no troubles at all. After the upgrade, some files still do not print but the file doesn't seem to exist anywhere, either.

I'm just not sure how to track this down and determine what exactly is happening. Any ideas?

I have attached images for steps 2-4 above, showing the configuration.

What about the main settings of the Job - have you checked "Put Job in queue"? If not, please do that.

---

What about the main settings of the Job - have you checked "Put Job in queue"? If not, please do that.

Absolutely. That is still set from the last time you remoted in and looked at it. 🙂 I've attached an image of it.

I would uncheck "Changed" from the File Trigger. This will cause multiple Triggers on the same file (when new).

---

I would uncheck "Changed" from the File Trigger. This will cause multiple Triggers on the same file (when new).

Okay, I'll give that a spin and see if it causes any improvement. Thanks Henrik!

I would uncheck "Changed" from the File Trigger. This will cause multiple Triggers on the same file (when new).

Okay, I'll give that a spin and see if it causes any improvement. Thanks Henrik!

Okay, I tried that at two different locations and I quickly got a call saying nothing was printing at all.

Logged in, and all the files were still sitting in the download directories.

I reset back to previous settings, and everything is working again.

You wrote before that "the file does not exist anywhere"? That is kind of strange? I mean, if it is not at the incoming folder and target folder - how do you then now it has been downloaded?

I suggest you log to a file when a new file has been triggered with date. Then you know if it has been handled or not.

I find it strange that you must use the "changed". There must be something specific how the FTP handles the files.

---

I agree, it is very strange. I'm still trying to gather more data on this when it happens, but it is difficult because usually they just reprint the ticket and then it does exist.

The danger is that if they don't notice it is missing, the order might not get made at all which will result in an upset customer when they come to get their food.

I know the files are being downloaded by VisualCron, because the FTP logs on the server show it getting picked up (every time), and the file is removed from the server.

I currently have all the print jobs logging to a file. When a job doesn't print, there just isn't anything for it in the log file.

I think having to use changed is weird too, but I'm not sure why removing it makes the file trigger invalid.

I just am unsure how to troubleshoot it at this point. At least with 5.6.2 when the job didn't run, the file was left behind. I could then use the file touch to force it through again, I think. Maybe I will have to downgrade and try that.

I just would prefer to fix it the normal way, if you have any other ideas. 🙂

Just a random thought here, Since you're looking for a file trigger... is it possible that the file showing up in the downloaded folder is triggering VC to do sometihng with it prior to the file being fully downloaded/written? I've worked with some of our own custom internal Java apps that some of our developers have written... and I've had to copy files with one filename... and AFTER copy was successfull, rename to a diffferent file extension since that rename is instantaneous. That way the Java app doesn't try to read the file too quickly.. only after that particular file extension shows up does it 'see' the file and at that point we already know the file is fully copied. Just curious if this could be somehow happening to you where VC is 'just too darn quick' for your FTP process to have released the file. Not sure how this would make the file not show up at all, but it just sticks in my mind as a potential thing to look into.

Another thought also with requiring 'changed' to be checked. I haven't tested this, but just speaking from some experience (not specifically with VC) i'm wondering if when the file is first detected by VC, if the 'date' of the file might look like 1-1-1969 or whatever that default date Microsoft uses for files being written sometimes. Then, when the file is fully copied, the RIGHT date shows up. This could be considered a 'change'.

I may be way off base, but thought i'd at least suggest it. :)

Brian