After activating a workflow, it is not executing when the corresponding run-time event is triggered.

(This cell is intentionally empty.)

Make sure Reload Runtime Events has executed. To tell if a workflow process is triggered, turn on workflow logging for EngInv, StpExec, and PrcExec. For more information, see Increasing Tracing Levels for Workflow Management Server Components.

After revising a workflow and reactivating it, the revised workflow information has not been read.

(This cell is intentionally empty.)

For workflows running in the Workflow Process Manager server component, reset the parameter Workflow Version Checking Interval. By default the interval is 60 minutes.

When a workflow is triggered by the run-time event DisplayApplet, the workflow is triggered the first time but not subsequently.

Since the DisplayApplet event is a UI event, and the default Web UI framework design uses a cache, the event only fired when the first time non-cached view is accessed. The workflow was triggered only when the event fired and worked correctly.

To make the field still work in this scenario, you can explicitly set EnableViewCache to FALSE in the .cfg file.

After triggering a workflow from a run-time event, the row ID of the record on which the event occurred is not retrieved.

The run-time event passes the row ID of the primary business component and not the row ID of the business component on which the run-time event is acting.

Retrieve the row ID of the active business component using search specifications. For example: the Active_row-id process property is equal to [Id], defined as Type equals Expression and the business component equals the business component name.

The following error message is displayed: Cannot resume Process [x-xxxxx] for Object-id [x-xxxxx]. Please verify that the process exists and has a waiting status.

This error typically occurs in the following scenario:

1. A workflow instance is started and paused, waiting for a run-time event.
2. The run-time event fires. The workflow instance is resumed and run to completion.
3. The run-time event fires for a second time. The Workflow engine tries to resume the workflow instance and fails, since the workflow instance is no longer in a Waiting state.

Deleting existing instances does not help. Ignore the error message and proceed. Step 1 through Step 3 must occur, in that order, in the same user session for the error message to be reported. As a result, the error message disappears when the application is restarted.

The Purge feature only works on stopped and finished instances. To delete persisted or incomplete instances, you first must manually stop the instances.

Unable to access a different business object from a workflow process.

The Workflow architecture restricts the use of one business object to a workflow.

Use a Sub Process step to access a different business object.

The following error message is displayed: Unable to initiate the process definition [process name].

(This cell is intentionally empty.)

Make sure the following conditions are true:

• The workflow process exists.
• The process status is set to Active.
• The process has not expired.

One of the following error messages is displayed:

• OMS-00107: (: 0) error code = 4300107, system error = 27869, msg1 = Could not find 'Class' named 'Test Order Part A'
• OMS-00107: (: 0) error code = 4300107, system error = 28078, msg1 = Unable to create the Business Service 'Test Order Part A'

(This cell is intentionally empty.)

Make sure at least one .SRF is copied to the Siebel Server\objects\[lang] directory.

The following error message is displayed:

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

A workflow process attempted to update a record that was updated by another user or task since the record was initially retrieved by the workflow process.

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