I have a job with multiple tasks, one of which has a timeout (set at the task level). I have run the job several times and it hits the task that times out and stalls there for five minutes, as it should, then times out. When it times out, though, it continues on to the "On success" condition in the flow tab, instead of the "On error" condition.

• I have verified that the task is timing out. It shows Exit code 77777 and "Exception in Task" in the task history. It does, however, show Output (error) as "No output".
  
• The Flow tab for the task clearly shows On success > Continue with next Task and On error > Goto Task 'ERROR EMAIL - Error while syncing', which is the behavior I want.
  
• The TimeOut tab shows use timeout is checcked and the timeout is set to 5 minutes. When the task runs this seems to work as it stays on this task for exactly five minutes then moves on to the next task.
  
• The On error tab is set to the default (Only selected errors > Unhandled errors, Task times out, Non zero exit code, Connection in Foreground execution failed.
  

How can I have a timeout trigger the On Error flow?

Which type of Task is this?

---

It's an Execute task to run Robocopy. I have already handled for Robocopy's exit codes (they don't use non-zero to mean error). But the timeouts resulting from the VisualCron task timeout setting are not flowing to the On Error task.

I tested by using On error together with Notification and I got the Notification. Have you checked "Timeout exception" in the On error tab of the Task that fails (the executable)?

---

As I said in my original post, the On Error tab has Task times out selected. I've attached screenshots to verify. I've also attached the task list that shows that the "Sync with Perseus" task fails, and that five minutes later the success condition runs, but that the fail condition never runs.

So, I discovered the problem. Because Robocopy does not use windows standard exit codes (0 is success, all else is error) I had to create my own exit code collection. That's fine. But, what I did not realize is that I needed to add 77777, the VisualCron default error, as an error code in my collection.

Is there a way to have a default behavior for exit codes not covered by your exit code collection? While it's not a big deal to add 77777 to any exit code collection it's not always possible to list them all. Robocopy, for instance, will sum error codes together to create new arbitrary exit codes that combine two messages.

Also, the interface wouldn't easily support adding a hundred or a thousand exit codes. Typically, you want to capture one or two of them, then let the rest be considered either a success or failure (likely a failure).

How can we default all un-enumerated exit codes to be a failure when using a custom error code collection?

So, I discovered the problem. Because Robocopy does not use windows standard exit codes (0 is success, all else is error) I had to create my own exit code collection. That's fine. But, what I did not realize is that I needed to add 77777, the VisualCron default error, as an error code in my collection.

Is there a way to have a default behavior for exit codes not covered by your exit code collection? While it's not a big deal to add 77777 to any exit code collection it's not always possible to list them all. Robocopy, for instance, will sum error codes together to create new arbitrary exit codes that combine two messages.

Also, the interface wouldn't easily support adding a hundred or a thousand exit codes. Typically, you want to capture one or two of them, then let the rest be considered either a success or failure (likely a failure).

How can we default all un-enumerated exit codes to be a failure when using a custom error code collection?

You cannot right now. Please make a separate Feature request about this.

---