Flow Engine Event Handler with job_context null results in additional unnecessary jobs


Description

Flow Engine Event Handler with job_context null results in additional unnecessary jobs

Steps to Reproduce

1. Steps to reproduce 8 parent Flow Engine Event Handler jobs per node. 

- Provision a new orlando instance or use an existing Orlando instance. In the instance - you will note there will be 4 Flow Engine Event Handler jobs where parent is empty and System id=Active nodes. This would be the OOB configuration.
- Upgrade the instance to Paris. After the upgrade, you will note that there are now 8 Flow Engine Event Handler jobs where parent is empty and System id=Active nodes. 

2. You can check any instance that has been upgraded to Paris and you will see the same pattern below for the parent Flow Engine Event Handler jobs (where parent is null and system_id=Active Nodes)

i. 4 Flow Engine Event Handler jobs where the job_context is empty. These are the ones that have existed before the Paris upgrade.

ii. 4 Flow Engine Event Handler jobs where the job_context contains "fcQueue=flow_engine". These are the ones that are inserted by the job - Check Active/All Node Jobs after the upgrade to Paris.

iii. you will also see 2 distinct sys_created_on dates for i and ii above

Workaround

See workaround in KB0868307


Related Problem: PRB1491477