A workflow process can error for a number of reasons. Most common errors include:
- SMTP Servers are unresponsive to outbound messages being set.
- Release related data errors (data types don't match, field lengths exceeded).
- Exceeding maximum performance capacity of server.
Workflows can leverage one or more Error Import nodes to create retry behaviors, or move documents to validation queues where admin level users can take action.
Settings
Workflow designers must provide a Title to add the node to a workflow. Optionally, a Target Node Name may be specified. When using multiple Error Import nodes in a single workflow, ALWAYS specify a Target Node Name for each node. Designers should also consider the Frequency specified. It may be unnecessary to check for errors at the default rate, and performing checks less frequently may improve overall system performance.
Sample Workflow
In this example, 3 Error Import nodes are leveraged. Each node is monitoring for processes in error from the node they target. In this example, we are going to perform a perpetual retry any time an error occurs in sending an email (1), sending an email (2), or releasing to an Archive (3).
In a different variant of the same process, the desired process may be to queue any errors to an Admin level user for management. In this example, only a single error import node is leveraged, and the Target Node Name in its settings is left blank. All errors in this workflow will route to a specific validate node when a trained user can perform the necessary steps to correct any errors.
