Workflow error handling
The personalized JavaScript that users create in workflow activity variables is vulnerable to run-time syntax errors. Available error information is available in a tooltip when you point to a workflow activity in an error state.
In the base system, workflow activities do not provide condition routing on the error state. As a result, the workflow progresses based on the state of the current record. For example, a workflow contains an Approval - User activity that uses an advanced script to add additional approvers. A syntax error in the script results in no approvers being added. Because a state of no approvers is a valid return, even without the syntax error, the approval activity is skipped and the workflow progresses along a positive path. However, this might not be a valid response for the workflow designer who does not want the workflow to progress along the positive path without approvers.
- Approval - User
- Approval - Group
- Catalog Task
- Create Task
- If
- Run Script
- Notification
Available error information
This table shows which activities support error exits.
| Activity | Workflow log | Red error indicator | Activity state | Activity result | Fault description | Reroute on error |
|---|---|---|---|---|---|---|
Approval - User Approval - Group |
Yes | Yes | Error | Skipped | Yes | Yes |
Catalog Task Create Task |
Yes | No | Finished | none | No | No |
| If | Yes | Yes | Error | none | Yes | Yes |
| Run Script | No | Yes | Error | error | Yes | Yes |
| Notification | Yes | Yes | Error | error | Yes | Yes |