2020.1

your process, and will be triggered if the Send to Process option is checked in that tab and an
Error process is selected in the drop-down list.
To create an Error process, simply replace the initial input task by the InputErrorBin Input task,
and that process automatically becomes able to handle error jobs sent to it. It is up to you,
however, to decide how that error job will be handled.
For example, you could place the job file in a specific folder, then send an email to a supervisor
indicating that a job has failed. Or you could update a database with an error status so that it
appears on a customer's online order. You could also zip the order up and send it to an
administrator, while simultaneously advising the person that sent the job that it failed.
You can have as many error processes as you can normal processes - that is, you are limited to
512 processes, subprocesses, startup processes and error processes combined.
Information available in an Error process
The following information is available from within your Error process when it is triggered.
l A series of variables containing information about the error, the task that triggered it and
the process that contained it (see below). These are "System variables" on page699.
l "Job Info variables" on page697 (%1 to %9).
l The data file as it was before starting the task.
l Global variables (which are, of course, available anywhere).
Note
Local variables in the process are not sent to error processes, even if the error process
has a variable of the same name.
Error handling variables
The error handling variables are read only and are filled by the On Error mechanism.
They can be accessed anywhere, but they only appear in the contextual menu of a task
property field when the current process is an error-handling process (that starts with the Error
Bin Input task). See also: "Variable task properties" on page707.
Page 99