Error Recovery
Recover processes in an error state and move them to the node of your choosing.
A process might error for many reasons. You might set character data in a numeric or date field. You might loose connectivity to your SMTP gateway. A variety of system and data specific conditions might cause a process to error. This node listens for process in error for a given workflow, redirects them to a specific node, and readies the process again.
This node will need to be downloaded from the Square 9 SDN before proceeding.
This node serves as an improved replacement for the “Error Import” node. The legacy node has been deprecated. While it may still be available in the SDN, all users are encouraged to use this version of the node.
Node Properties
Title
Add a title for this node. Your title should be brief but descriptive about what is being picked up. Titles are useful when reading the history in the history of a workflow for easier understanding of the overall process.
Description
Provide a synopsis of what this node is doing, or make note of any important details. This is useful for providing additional information such as workflow details, pick up Inbox, destination Archive, use case information, etc. A good description is helpful when returning to modify the workflow in the future.
Frequency
Includes settings for Days, Hours and Minutes. By default, this is set to 15 minutes. Setting the frequency is important for how often you’d like for this to execute. For example, if there is a nightly upload we’d want this to run once every 24 hours and can set the frequency to do so.
The workflow will run with the scheduled frequency each time the workflow is saved.
Ex. If you set the frequency to 1 hour and save the workflow at 2:42 pm, it will run immediately on save and then again at 3:42 pm and so one. If you were to modify the workflow at 3:15 pm and save, it would run immediately and then again at 4:15.
Data Validation
Data Validation is only an option in GlobalCapture.
The Data Validation checkbox is enabled by default to enforce Data Types or Length settings for Fields. When enabled, if data does not meet the type or length settings for the field, the process will error on this node.
Error Node
The Error Node is the Title of the node from which errors should be picked up.
When setting a value for the error node, you should use multiple Error Recovery nodes in your workflow (one for each error condition you seek to pick up). You can not name one error node and sweep all the rest with an second, empty error node.
Leaving the Title blank will redirect ALL errored documents to the Restart Node.
Restart Node
The Restart Node is the Title of the node to which the errored document is redirected.
The Title of the node specified in the Restart Node textbox controls the routing. The linked node in the workflow designer is not relevant.
The most common deployment for a workflow would be to have a single Error Recovery node routing all error conditions. The Error Recovery node can be linked to any node on the design surface, but the Restart Node is what governs where error processes are sent. For ease of understanding the workflow for future users, it might make sense to have the error recovery visually linked to the “Restart Node”.
Alternately, error import can also target an End node. Both are valid deployment options.


Use Case
Using the Error Recovery node to reprocess all errored documents in this workflow back to the Validate node
In this example, I've configured the Error Recovery node to take any errored documents from this specific workflow, and redirect them to the Validate node. This is useful for automatically reprocessing errored documents, without having to manually reprocess them or remove and re-add them back to the same workflow.

Node properties Example

Workflow Example
Date | Version | Description |
---|---|---|
01/20/2023 | 1.0 | Initial release. |