Workflow Monitor Agent Suddenly Stops Working
Last updated on JULY 11, 2017
Applies to:Siebel Workflow - Version 184.108.40.206 SIA  and later
It was noticed that Workflow Monitor Agent has suddenly stopped processing records properly despite the fact it is running.
It was found found that 3 out of 4 Workflow Monitor Agent (WorkMon) stopped processing records all of a sudden despite having been running fine for the last few months.The WorkMon task picks the records off of the S_ESCL_REQ table properly. It then says it processes them. These record should qualify.
In fact, since upgrade they did qualify and were processed properly. However, suddenly the workflow monitor agent stopped processing the records correctly.
On turning up the logging on the workflow monitor agent, nothing was seen anywhere in the log where the policy is being evaluated. This leads to believe that the Workflow Monitor Agent is not recognizing the workflow policy group
Re-starting the Workflow Monitor Agent component had no effect.
User also observed odd behavior with expired policies that suddenly became active for which WorkMon started processing requests.
Troubleshooting Steps taken:
1. Dropped and regenerated triggers.
2. Recreated the policies which included the policy conditions, group and action.
3. Recreated the custom WorkMon component.
4. Verified that the active policies has valid activation and expiration date and they were as follows.
Activation = 6/27/2005
Expiration = 9/30/2099
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms