Why Workflow Policy Action is not Executed after First Action Execution and Records Removed from S_ESCL_REQ
Last updated on MAY 14, 2018
Applies to:Siebel Workflow - Version 7.5.3  and later
Information in this document applies to any platform.
Database(s):All Supported Databases
App Server OS(s):All Supported Platforms
Latest release tested against:V8 (Enterprise)
Keywords:Action Interval, Policy, Action only executed once
Checked for Relevance on 13-Jan-2012
This document was previously published as Siebel FAQ 1595.
When the workflow policy is executed, the first execution is successful and the subsequent ones never triggers any action, at the same time why the records from S_ESCL_REQ table gets deleted.
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