I have several jobs that copy files, and I am using the {TASK(blahblah.NoCopiedFiles) (or maybe its NoFilesCopied), but at any rate, the job runs at 8 am, and reports that it copied 8 files. 15 minutes later, the job runs and reports 8 files copied. The only problem is that there were no files to copy in the source path, both because I used the delete source file option on the task, and because I've checked other logs and there were no files present.

This will continue for the next 2 or three times the job runs, and then it stops.

I've had the same issue using User variables to hold the value, but that seems to show the same behavior.

Its a bit annoying to keep getting a repeat of an old value, and it leaves me wondering just how accurate the first count returned might be.

is there a setting I'm missing, or is it somehow reporting the number of files in the destination directory, or what? I am running version 7.7.3 on the server, and 7.7.2 on the client where I created the jobs.

Which exact Variable do you use?

Can you please test this version: http://www.visualcron.co....aspx?g=posts&t=5087 

---

I am using {TASK(bdca9514-bbff-40ad-bd7e-94efd91039c9,Result.NoCopiedFiles)} as my variable. At least for this specific job.

Since the job runs on the server, I'm not sure if I can get the admin to agree to install the test version, but I think I have a virtual machine somewhere I can try it out with. I will let you know.

Thanks,
Luther

Thanks, please let us know.

---

It works. I had found a workaround using the String.RowCount function with the copy step's StdOut, but I have concerns about its reliability.

How soon will this version be released for consumption?

Thanks very much for your help.

Luther

It works. I had found a workaround using the String.RowCount function with the copy step's StdOut, but I have concerns about its reliability.

How soon will this version be released for consumption?

Thanks very much for your help.

Luther

Some day this week. Thanks

---