Activities Spawned with ActivitySequence Do Not Stop the Batch Process if an Error Happens

(Doc ID 2101986.1)

Last updated on JUNE 28, 2017

Applies to:

Oracle Insurance Policy Administration J2EE - Version 10.0.0.0 and later
Information in this document applies to any platform.

Symptoms

On : 10.1.2.3 version, Activity

Actual Behavior
When an error occurs in an Activity spawned by ActivitySequence the batch process continues to process activities.
Ex.
Activity A spawns activity B using ActivitySequence.
Several days later activity C is created and scheduled to be process through the batch cycle.
Activity B has an error condition that causes a failure but the process is not interrupted.
Even if there is an error, the activity B is processed with status Queued ActivitySequence, activity A has status Activity Sequence Error.
Activity C is processed, the subsequent activities are processed too.
 
Expected Behavior
Scenario when activities are processed manually:
Activity A spawns activity B using ActivitySequence.
Several days later activity C is created and scheduled to be process through the batch cycle.
Activity B has an error condition that causes a failure and the process should be interrupted.
Activity C is never processed.

The issue can be reproduced at will with the following steps:
1. Create an activity which uses ActivitySequence to spawn another activity.
2. Create a third activity to be processed by nightly cycle.
3. Run nightly cycle - the spawned activity should cause and error and prevent further processing, but does not.

Cause

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