New problems I'm afraid. The Copy loop I'm using relies upon the DownloadedFileNames variable from the previous task, which is a FTP Download task. But this variable seems to be temperamental.
On today's run, even though it downloaded 10 files, the DownloadedFileNames variable only contained the name of the file with the latest modified date as shown on the FTP, and thus that is all the Copy task moved across for emailing. Yesterday it worked fine.
I've looked through the log, and all files were downloaded in a single run of the Download task, the file contained in the variable was the 2nd file to be downloaded in the task, so not even a special position like first or last.
This task now has two triggers after what you said yesterday about exceptions. It triggers on the FTP event, but also has an initial timed trigger that happens the moment the exception period is over at 5:15pm. Both triggers were in place yesterday and it worked fine.
I think this issue is somehow linked to the FTP Trigger event, as the filename in the variable would have been the last file to trigger it, but the exception would have prevented task activation.
Any thoughts?