1. Business Process Framework: Workflow Guide
  2. Troubleshooting Problems That Occur When a Workflow Process Runs

Troubleshooting Problems That Occur When a Workflow Process Runs

The following table describes some common problems that might occur when a Workflow Process runs and how to resolve those problems.

Symptom Diagnostic Steps and Cause Solution

The DisplayApplet Runtime Event starts a Workflow Process the first time the applet is accessed, but not on subsequent times the Applet is accessed.

The DisplayApplet Runtime Event is a UI event. If the default Web UI framework uses a cache, then Siebel only starts the event the first time it accesses a non-cached view.

To make the Runtime Event start each time the Applet is accessed, set the EnableViewCache parameter in the .cfg file to FALSE.

After Siebel CRM starts a Workflow Process from a runtime event, it does not get the Row Id of the record on which the event occurs.

Runtime Events pass the Row Id of the Primary Business Component in the active business Object to the Workflow Process "Object Id" Process Property. For more information, see Defining the Primary Business Component.

To get the Row Id of the active business component, you can use a search specification.

Siebel CRM displays the following error message:

Cannot resume Process x-xxxxx for Object-id x-xxxxx. Please verify that the process exists and has a waiting status.

Deleting existing instances of the Workflow Process does not help. This error typically occurs in the following situation:

  1. A Workflow Process instance starts and pauses, waiting for a runtime event.

  2. The runtime event starts. Siebel CRM resumes the instance and runs it to completion.

  3. The runtime event starts a second time. The Workflow Engine attempts to resume the instance but fails because the instance is no longer in a Waiting state.

These steps must occur in the sequence described and in the same user session in order for Siebel CRM to report the error message. As a result, the error message disappears when the Siebel CRM application restarts.

Ignore the error message and proceed.

The Purge feature only works on instances that Siebel CRM has stopped and finished. To delete a persistent or incomplete instance, you first must manually stop the instance.

Unable to access a different business object from a Workflow Process.

Siebel Workflow Processes are constrained to a single business object.

Use a sub process step to access a different business object.

Siebel CRM displays the following error message:

Unable to initiate the process definition process_name.

N/A

Make sure that each of the following is true:

  • The Workflow Process exists.

  • The repository definition of the Workflow Process is not marked as Inactive.

Siebel CRM displays the following error message:

The selected record has been modified by another user since it was retrieved.

A Workflow Process attempted to update a record that another user or task updated since Siebel CRM initially retrieved the Workflow Process.

Define an error exception connector to handle the update conflict. For more information, see Defining an Error Exception Connector to Handle an Update Conflict.