Table 55. Descriptions for Resolving Workflow Process Simulation Problems
|
Diagnostic Steps or Cause |
|
When trying to simulate a workflow, upon starting the workflow, the simulator does not run. |
If a Start step has an outgoing branch with a run-time event, the simulator waits on the event and never reaches the next step. |
Choose one of the following approaches:
|
When attempting to rerun the simulator, an error dialog displays Still waiting on Workflow Process Simulator, or The run-time client is not responding. |
Navigating in the Siebel client during or after running the simulator can cause a failure during subsequent attempts at running the simulator. |
Do not navigate in the Siebel client while the simulator is running or after the simulation ends. For more information, see Process Simulator Usage Considerations. |
After completing the user interact step, the simulator fails to proceed down the workflow. |
The branches out of the user interact step can be missing associated run-time events. |
Make sure branches out of the user interact step have the respective run-time events associated with actions performed on the user interact step. |
After the Siebel client launches, control does not return to Tools, or a dialog in Tools indicates the client is still launching, even after a long wait. |
(This cell is intentionally empty.) |
Log out of the Siebel client session and close Siebel tools. Open Windows task manager. Click the Processes tab, right-click the dbeng9.exe Image Name, choose End Process, then click Yes. Right-click the siebel.exe Image Name, choose End Process, then click Yes. Restart Tools and run the Simulator again. |
An error message appears during simulation execution, similar to Error loading siebel operation step definition [step name]. The specified step definition is not valid. |
Errors in the workflow process configuration are revealed during the simulation, which can include errors in how objects are defined or how objects are used by the workflow process. |
Close the simulator, correct the configuration errors, then run the simulation again. |