---
sourceDocument: Australia ServiceNow AI Platform Capabilities
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/servicenow-platform

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia ServiceNow AI Platform Capabilities

ft:clusterId :

    - platcap

bundleId :

    - platcap

workflow :

    - Platform


---

# Workflow error handling

# Workflow error handling {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 Minute Lesedauer

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.  
Workflow error handling detects and logs syntax errors and provides a state that the workflow designer can use to add error conditions to the workflow. Use error handling to locate syntax errors in advanced script fields for these workflow activities:

* Approval - User
* Approval - Group
* Catalog Task
* Create Task
* If
* Run Script
* Notification
{#c_WorkflowErrorHandling__ul_rcm_ffz_qq}

## Available error information {#c_WorkflowErrorHandling__section_xl1_ldb_2cb}

This table shows which activities support error exits.
{#c_WorkflowErrorHandling__table_tbm_bgz_qq__entry__7}

| 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 |
[Tabelle : 1. Available error information]

{#c_WorkflowErrorHandling__table_tbm_bgz_qq}
* **[Workflow error tracking features](https://servicenow-prod.fluidtopics.net/TBgOz1scxELikl40JwjXRw)**   
  Error handling provides visual cues within the workflow, such as error descriptions for activities in pop-ups, and detailed log records.
* **[Create an error condition exit](https://servicenow-prod.fluidtopics.net/t_kRHl_fuHo3gid9jB1lag)**   
  An administrator can reroute the workflow when a script error occurs by creating an error condition exit for specific activities within the workflow. This allows the workflow to process script errors in a predictable way and not create undesirable results.
* **[Reconfigure an approval condition](https://servicenow-prod.fluidtopics.net/YOJbFgq_kdiCW~~Dl1bKOw)**   
  Approval activities react differently to script errors than the other activities.