Siebel Business Process Framework: Workflow Guide > Administering, Testing, and Migrating Workflow Policies > Monitoring, Testing, Troubleshooting, and Migrating a Workflow Policy >

Fixing a Workflow Policy That Does Not Trigger

This topic describes how to troubleshoot a workflow policy that does not trigger.

To fix a workflow policy that does not trigger

1. Make sure your test record meets the workflow policy conditions.
2. Make sure the Siebel client configuration file references the correct Siebel Server.

   If the Siebel client configuration file does not reference the correct Siebel Server, then an error that is similar to the following might occur:

   ESC-00053 Error loading rule definitions

3. Examine the date and time that Siebel CRM activated the workflow policy.
4. Examine the monitor task:
   1. Determine if the monitor is awake and running on the correct group.
   2. Search the Task Information log for the ROW_ID of your test record:
      • If ROW_ID does not exist, then run GENERATE TRIGGERS.
      • Update your test record.
5. Examine the Action Agent task:
   1. Determine if the Action Agent is awake and running on the correct workflow policy group.
   2. Search the Task Information log for the ROW_ID of the test record.
6. Make sure Siebel CRM creates the database triggers.

Tracing a Workflow Policy

Siebel CRM uses the General Events event to log a workflow policy. To view informational messages, you can set the log level to 3. To view debugging information, set the log level to 4. For more information, see Tracing a Workflow Policy.