We have SFTP task with two commands. The Task Flow says "On error, wait 0:00:30 and retry Task"

If the first command gets an error, the task is marked in error, but there is no retry of the task.

Server log with debug is attached.

I am now testing out Retry on the command settings (rather than at the Task level) but still, this issue seems like a bug.

Thanks.

I see this: 20/10/2016 19:14:35 Err TaskRetry failed after 100 times. Aborting Job

Can you post the settings from that flow window? You only have one on error flow?

---

Hi Henrik

Yes, the log says "failed after 100 times" but you'll notice the timestamp of all log entries related to that task happen at 19:14:35. It's not possible to retry 100 times with a 30 second pause in that duration.

Task flow is attached.

Thanks.

We tried to reproduce this but cannot. In our example we have 2 commands. First uses wrong source folder and will fail. Second uses the correct one. We have set retry on the Task. First one fails and then it retries for 3 times.

I am not sure how to proceed with this unless it is really simplified from your end (perhaps you can try our example to see if it behaves correctly for you?).

---

Hi Henrik

I tried using the ftp setting "Resume if transfer failed" but I still do not see the task repeated. Could the problem be with having multiple FTP steps in the same VisualCron task? It's difficult to rely on VisualCron if there's no way to capture and handle this error. Is there a way you can recommend setting up FTP so that we can guarantee the error handling works as expected? (maybe, single download per task?) I'm really desperate to find a solution to this.

Thanks.

I think, to validate this, you need to start testing with one file. We have tested this a lot by for example turning of the FTP server while transfering and then later turn it on.

It should not matter how many files but it is way easier to debug with one.

---