When I am doing ftp transfers, I am getting a successful return even if no file transfers occurred. Is there any way to have the task fail when, in effect, no file transfer takes place, rather than getting a successful return?
This issue is present for sFTP and regular ftp.

Thanks.

This is the way it works currently. It does not throw any error. I am moving this topic to Feature requests forum.

---

I haven't seen this topic listed in the feature requests.

I have to disagree with you about it being a 'feature', since the objective of an FTP task is to transfer files, if no file transfer takes place, it obviously failed. I can't think of any condition under which the failure to transfer a file using an FTP task could be considered a 'success'.
When I go to my supervisor to explain why a vendor didn't receive their file, which has monetary implications, that they had to have received the file because the task shows it to have executed successfully. It doesn't not give your product, or myself, any validity.
I am currently revamping all my ftp tasks, which are numerous, to check a condition after the task executes, whether successfully or not, to see if the given file was transferred and throw an error message if it didn't. It would save myself and I'm sure alot of people extra work to test if a given ftp task actually transferred a file before it could be considered 'successful' or not.
It would make things much easier if the absence of a file transfer on an FTP task triggered a failure of the task and therefore the job. This way, we can stop everything and manually intervene.

Are you saying the file exists and is in your match criteria but does not transfer or are you saying there was no file there to transfer (but still succeeded)?

The file filter was fixed between version 6.0.9 and the version I"m running now, 6.1.1. I wrote the original job using filters that picked up the file I was after. Since 6.1.1 started working differently from version 6.0.9 the file it was looking for did not get picked up and therefore, no file was actually transferred. The FTP task registered as successful, though.

This has always been like. Many of our users schedule ftp transfer on many times a day, just to find new files that match the filter. They may not be interested in throwing an error if a file is not transferred because it just did not meet a filter that they had.

For this reason, this is a Feature request for us as it has not been requested before.

We still think that this a good addition and will implement it.

---

I see your point Henrik.
If there was a setting on an 'upload' or 'download' ftp task type that would allow you to set it to throw an error when no file transfer occurred, it would come in handy, I would think.