We've been running a job with the FTP Remote File Trigger to monitor an FTP we need to download files.

The owner of the FTP has complained about how much we are polling their FTP and want us to restrict it to a particular time window.

If I apply a time exception to this job, I know the exception will stop the tasks from running, but will it also stop the FTP Remote File Trigger from polling the FTP?

No, currently, the FTP Trigger will only prevent Triggering - not the actual polling.

Perhaps you can decrease polling interval?

---

We could however discuss internally if this can be changed. Moving this topic to Feature requests.

---

Decreasing the polling interval wouldn't make the kind of impact the FTP owner is after. They essentially don't want their FTP being automatically polled during a period where its known for sure the files won't be available.

The other way is to simply use the FTP Task and a normal Time Trigger. Then you can schedule gaps in time. If you do not want to schedule gaps in the time trigger you can combine it with time exception as well and you get what you want.

---

That would require storing the files locally and setting the FTP Download Task to not overwrite. And then relying on the Result.DownloadedFiles variable to determine what is new after a download, so to email it. A previous post of mine is quite in-depth on the nightmare I had when setting this job up where I discovered that the Result.DownloadedFiles variable was not dependable.

That would require storing the files locally and setting the FTP Download Task to not overwrite. And then relying on the Result.DownloadedFiles variable to determine what is new after a download, so to email it. A previous post of mine is quite in-depth on the nightmare I had when setting this job up where I discovered that the Result.DownloadedFiles variable was not dependable.

About Result.DownloadedFiles what results you had with logging this (with File write Task) as we have no know problem with this Variable.

---

The logs (with debug on) showed the task would successfully download multiple files in one go, but the Result.DownloadedFiles variable used by the next task would only contain one file name, or sometimes none. It kept causing the job to fail on me, I would rather not start looking at that route again.

What about dependencies? Could they be used to control when the FTP Remote File Trigger is looking at the FTP.

The logs (with debug on) showed the task would successfully download multiple files in one go, but the Result.DownloadedFiles variable used by the next task would only contain one file name, or sometimes none. It kept causing the job to fail on me, I would rather not start looking at that route again.

What about dependencies? Could they be used to control when the FTP Remote File Trigger is looking at the FTP.

This kind of problem can only exist if not Active and LastTrigger is used in the Variable. From what I remember you had a loop and it is possible that something went wrong there - that is why we suggested adding a File write Task inbetween so we could confirm the values. But we will do some more tests.

Conditions could be used but they can only prevent Job from running - not the polling.

Another feature we will add soon is to Activate and Deactivate a Trigger on a specific Job.

---

We added a change for next version (7.0.0) that we do not poll if there is a matching time exception.

---

When is 7.0.0 due out?

1st of August is the plan.

---