Starting a workflow throws an exception. Why is no instance created?
Problem A workflow encounters an exception, but no workflow instance exists to indicate that the workflow was instantiated. Solution Workflow instances are created and persisted in the database only after a workflow reaches a quiescent state or done node. If a workflow encounters an exception before it reaches a quiescent state or done node, the workflow instance is rolled back. To solve this problem, force a quiescent state by inserting an action, such as No Operation or Assign Task to User, that causes the workflow instance to wait. Additional Information See Using the WebLogic Integration Studio and Understanding the BPM Transaction Model in Programming BPM Client Applications.