Using Error Macros in Next Action

Using Error Macros in Next Action - Run Task

Use the built-in [Error... macros to send the error code and description of any error that occurred in the subject or body of a Next Action notification.

For example, a Next Action message body of:

At [yyyy]-[mm]-[dd] [hh]:[tt]:[ss], task '[TaskName]' 
encountered error #[ErrorCodeFile] - [ErrorDescriptionFile] - while transporting '[OrigName]' (FYI, the current 
task error is #[ErrorCodeTask] - [ErrorDescriptionTask])

...will be interpreted as:

At 2005-01-07 12:37:26, task 'Test Error Macros' 
encountered error #2234 - CopyFile returned 
Access is denied. - while transporting 'readme.txt' 
(FYI, the current task error is #2234 - CopyFile 
returned Access is denied.)

If you settle on a preferred combination of messages using error macros, you can propagate their use by setting them up as Global Parameters and configuring your tasks' Next Actions to work off global parameters rather than a different message for each task.

Next Action Tips

Next Actions can generate failures. For example, if a task successfully transfers 5 files but cannot send the email to notify the operator, task is marked as failed. To prevent this problem for Send Email next actions, point your mail host to a reliable external server or to the localhost SMTP server.