Business Process Errors

The error messages for most Business Process An organized flow of activities or tasks that achieves a business goal. An automated business process minimizes the amount of paperwork and manual tasks to complete that process by way of automatic actions, online forms, and automatically generated messages. errors provide a solution. The following errors, however, can be the result of a number of different conditions.

Error Message Issue Probably Causes
Business Process Engine is unavailable. You cannot deploy a process model at this time. The Workflow Engine is down.
  • ILB is down.
  • NGINX is down.
  • Webagent is down.
  • Tomcat server is down.
  • Database is down.
Business Process Designer is unavailable. You cannot create, edit, or delete a process model at this time. Workflow Designer is down. (The Workflow Engine and Workflow Designer are on the same server.)
  • ILB is down.
  • NGINX is down.
  • Webagent is down.
  • Tomcat server is down.
  • Database is down.
Business Process Engine is unauthorized. You cannot deploy a process model at this time. The tenant is not present in the Workflow Engine.
  • The workflow service failed to create the tenant during tenant provisioning.
  • The tenant was manually deleted from the workflow service.
  • The user could not be created on the workflow service.
Business Process Designer is unauthorized. You cannot create or edit a process model at this time. The tenant is not present in the Workflow Designer.
  • The workflow service failed to create the tenant during tenant provisioning.
  • The tenant was manually deleted from the workflow service.
  • The user could not be created on the workflow service.
This Process Model cannot be deployed. Refer to the online help for more information. The system encountered an error while deploying a model. A Process Model will fail to deploy for the following reasons:
  • Any internal server error occurred.
  • The process contains a script task and the script contains restricted coding patterns such as:
  • import groovy.sql
  • import java.sql
  • import com.gmongo
  • Sql.newInstance
  • jdbc:edb
  • jdbc:mysql
  • jdbc:db2
  • jdbc:oracle
  • jdbc:postgresql
  • jdbc:hsqldb
  • jdbc:sqlserver
  • jdbc:jtds
  • MongoCredential.create
  • GroovyShell
The Business Process cannot be transferred. Refer to the online help for more information. The system encountered an error while transferring a process model through SDM Setup Data Manager moves and manages configuration data across software and hardware environments.. A Process Model will fail to deploy for the following reasons:
  • Any internal server error occurred.
  • The process contains a script task and the script contains restricted coding patterns such as:
  • import groovy.sql
  • import java.sql
  • import com.gmongo
  • Sql.newInstance
  • jdbc:edb
  • sql.execute sql.rows
  • jdbc:edb jdbc:mysql
  • jdbc:db2 jdbc:oracle
  • jdbc:postgresql
  • jdbc:hsqldb jdbc:sqlserver
  • jdbc:jtds
  • MongoCredential.create
  • GroovyShell
This task has failed runtime validation and cannot be completed. Refer to the online help for more information The system failed runtime validation while executing the workflow from Control Center.
  • Rest API call failure in Internal Rest connector, Generic Rest connector, and Service tasks.
  • No form attached to user task.
  • Missing error handling
  • Any design error that was not validated during the Process Model design time, such as missing evaluation of sequence flow
  • Any expression that could not be evaluated
  • Script task contains restricted coding patterns such as:
  • import groovy.sql
  • import java.sql
  • import com.gmongo
  • Sql.newInstance
  • jdbc:edb
  • jdbc:mysql
  • jdbc:db2
  • jdbc:oracle
  • jdbc:postgresql
  • jdbc:hsqldb
  • jdbc:sqlserver
  • jdbc:jtds MongoCredential.create
  • GroovyShell
Service unavailable Workflow service while executing the Business Process from Control Center. The Workflow service is either unavailable or the user is not authorized to access it.