I recently turned on extended logging so I can have more visibility into why things fail. I noticed that for tasks that have a loop based on "for each" of a master task (say list files task), an error is generated each time the looped tasks are skipped for this reason.

I don't feel this should be treated as an error in a task, but rather an informative message stating that the looped tasks were skipped due to no files being found. Otherwise, the log file is needlessly cluttered when filtered by errors only.

I understand that there may be cases when you would want this to be treated like an error, but you can easily accomplish that by simply setting the list files task to flag no files found as an error. In fact, that is the default for that type of task.

So what I'm suggesting is either move it always to be an info type log message, or call it an error ONLY if the master loop task treats "No files found" as an error. If that master task is configured to skip over "No Files Found", the looped tasks should also not consider that an error.

Make sense?

It makes sense.

I would summarize this in 2 requests:

1. be able to control if this should result in an actual error
2. perhaps not log that error for each Task but only first time

Thanks for the report - I am moving this topic to Feature requests.

---