2022.2

Table Of Contents
When an error occurs in a loop (or in a plugin that acts like a loop), the loop may log the
error, terminate the current iteration and proceed with the next iteration.
l
Stop Branch: If the task is in a branch of the process, the branch is stopped and the job
file is returned to the process after the branch. The branch will not produce any output. If
the task is not on a branch, the entire process will be stopped.
l
Stop Process: The process is stopped and no more processing is done. No further output
is produced.
l
Log Message: Check this option to enable logging a custom error message in the PlanetPress
Workflow log file and in the Windows Application Events.
l
Message: Enabled only when the Log Message option is checked. Enter a message that will be
logged in the PlanetPress Workflow log file. You can use any variables available in PlanetPress
Workflow to customize the message.
l
Store the message in variable: Select in which jobinfo, local or global variable you want to
store the message content.
l
ID: Enter an error ID. This ID will be visible in the Windows Event Viewer. However, the ID is not
visible in the PlanetPress Workflow log file.
l
Store the ID in variable: Select in which jobinfo, local or global variable you want to store the
error ID.
l
Reset to defaults: Resets all options in this tab to their default values.
When storing the message or ID, if they are stored in a jobinfo they will be available in any error hand-
ling process where errors are being forwarded. If your process continues after the error, the contents of
the variables selected in this window will be available to the rest of your process, or as long as they are
not overwritten.
All error codes are listed in the knowledge base of PlanetPress Workflow. Though some error mes-
sages are specific to a task in particular, others may apply to any and all tasks because they are related
more to the system than to PlanetPress Workflow itself. Some examples would be W3813, W3830,
W3991, W4005. These correspond to issues such as not having any space to write files, permission
errors on folders or files, etc.
Creating and using Error processes
An Error process is a special type of process that never runs on its own, and cannot be called using the
GoSub or Send to Process tasks. It can only be used in the On Error tab of a task in your process,
and will be triggered if the Send to Process option is checked in that tab and an Error process is selec-
ted in the drop-down list.
Page 84