Troubleshooting Problems That Occur During Simulation

The following table shows how to troubleshoot some common simulation problems by describing a symptom and then providing the corresponding solution to resolve the problem.

Symptom	Diagnostic Steps or Cause	Solution
When attempting to start a simulation, the Process Simulator does not run.	If a runtime event is defined on the connector that emanates from a start step, then the Process Simulator waits for the event and never reaches the next step.	Do one of the following: Remove the runtime event from the simulation. Add a Default branch. It is recommended that you define two branches: One branch with Type set to Condition that waits for the runtime event One branch with Type set to Default
When attempting to rerun the Process Simulator, an error dialog displays one of the following messages: Still waiting on Workflow Process Simulator The runtime client is not responding	Navigating in the Siebel client during or after running the Process Simulator can cause a failure during subsequent attempts at running the simulator.	Do not navigate in the Siebel client while the Process Simulator runs or after it ends. For more information, see Guidelines for Using the Process Simulator.
After completing the user interact step, the Process Simulator fails to proceed to the next step in the Workflow Process.	A branch from a user interact step might be missing an associated runtime event.	Make sure the branches from the user interact step reference the runtime events that are associated with actions that the user performs on the user interact step.
After the Siebel client starts, control does not return to Siebel or a dialog box indicates that the client is still starting, even after a long wait.	N/A	Restart processes that are currently running.
An error message that is similar to the following message appears while the Process Simulator runs: Error loading siebel operation step definition <step_name>. The defined step definition is not valid.	Errors in the Workflow Process configuration can occur during the simulation. These errors can result from errors in how objects are defined or how the Workflow Process uses objects.	Close the Process Simulator, correct the configuration errors, and then run the simulation again.