SOA 10g: Human Workflow Expiration Does Not Survive Server Restart

(Doc ID 1209274.1)

Last updated on MARCH 08, 2017

Applies to:

Oracle(R) BPEL Process Manager - Version and later
Information in this document applies to any platform.


You are using Oracle Human Workflow Task API to assign tasks to users and expire tasks based on pre-configured rules.

When you restart the server (BPEL engine) before the task expiry, then the expiry never kicks in and corresponding BPEL process remains in running state forever.


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