Excess Flow Engine Event handler jobs created after upgrade to ParisDescriptionIf the instance has recently upgraded to Paris, you may have noticed that there are many more Flow Engine Event Handler jobs (in sys_trigger) as compared to the previous release (for example Orlando). This may then cause delays in running other jobs and or High DB CPU load (see KB0868534) for instances with a large number of nodes as these jobs are running at a 2-second interval. Steps to Reproduce - Navigate to /sys_trigger_list.do?sysparm_query=name%3DFlow%20Engine%20Event%20Handler%5Eparent%3DNULL, you will see that there are 8 parent Flow Engine Event Handler jobs (compared to 4 in Orlando release). - The total number of Flow Engine Event Handler jobs may have doubled compared to the previous release. Workaround1. Navigate to the following URL: /sys_trigger_list.do?sysparm_query=name%3DFlow%20Engine%20Event%20Handler%5Eparent%3DNULL and validate that there are 8 jobs - 4 with empty job context and 4 with non empty job context (see screenshot below). 2. Select the 4 jobs with empty job context and delete. There will be a popup with the message: Warning! Deleting the selected records will result in the automatic deletion of related records. Click Delete to proceed. 3. After the 4 extra parent jobs have been deleted, the number of Flow Engine Event Handler jobs should now be the same as before the upgrade to Paris. 4. An alternative would be the workaround in KB0868534. Please review that KB to understand the implications. Related Problem: PRB1454750