Siebel Business Process & Functionality (MOSC)

MOSC Banner

Action Interval parameter of the Workflow Monitor Agent

edited Apr 30, 2013 10:46AM in Siebel Business Process & Functionality (MOSC) 3 commentsAnswered ✓
Hi,

According to the documentation and the description of the parameter, the Action Interval parameter of the Workflow Monitor Agent is configured in seconds. We did set the parameter to 3600 (thinking that it was in seconds) because we wanted to avoid the same action to be re-executed in each hour.

However, increasing the component log level, we noticed that Siebel is assuming the parameter is configured in minutes.

QLSlowQuery    Statement          4             0000000651673458:0      2013-04-12 01:01:08

select VIOLATED_DT

from CRBDPRD.S_ESCL_LOG

where RULE_ID = ? and

     BT_ROW_ID = ? and

     VIOLATED_DT > (current timestamp - cast(? as INT) MINUTES)

 

Consequently, records changed multiple times are not processed until 2,5 days have passed (3.600 minutes) instead of being processed after 1 hour (3.600 seconds).

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center