Problems with Objects not transitioned

Occasionally an Object will fail to transition between states when it 'should have'. This is typically caused by an application bug or an FSM race condition.

The following steps should be followed to diagnose the causes of the failure:

• Look for the event that should have caused the transition. In normal circumstances not all events are being logged. For more information on how to alter event logging, see FTM Event logging .
• Look for signs of problems (for example, Unexpected Error events)
• Determine what event should have caused the transition
• From what transition/action should that event been raised? - can you see any evidence that the initiating transition/action occurred? - for example the object state will typically indicate a state transition.
• The transition may have been rolled back - usually an Unexpected Error Event will be found as evidence.
• The Event metadata controls unit of work size and can be modified to prevent rollback.

If you need more information about specific events you can use the FTM Operations and Administration Console to look at the events - select the 'Events' option in 'Operational data' section of the left hand menu.