Issue

After updating your deployment of Pega Platform™ from version 8.x to Infinity™ release 23.1 and later, you see log file errors indicating that the OOTB Job Schedulers pzMergeMetricsConfigPulse   and pzCheckProfileMergeKafkaAlert  fail registration with reason: Invalid mapped node type.  

In Pega Diagnostic Cloud (PDC) you see errors relating to PEGA0098 alert: Job scheduler failed to register for the next run. 

This occurs in any environment not provisioned with the RealTime node type applicable for these Job Schedulers.  

Steps to reproduce

1. Update Pega Platform to Infinity ‘23™ or later releases. 

2. Pega Diagnostic Cloud displays events indicating that the registration failed for Job Schedulers pzMergeMetricsConfigPulse  and pzCheckProfileMergeKafkaAlert . 

3. Open the Job Scheduler rule and note the Guardrail warnings.

4. Open the Associated with node types configuration. (On some environments the RealTime checkbox exists and is selected).

Errors

PEGA0098 - Job Scheduler pzMergeMetricsConfigPulse registration failed. Error message: Invalid mapped node type RealTime 
 
PEGA0098 - Job Scheduler pzCheckProfileMergeKafkaAlert registration failed. Error message: Invalid mapped node type RealTime 

Root Cause

The application assigns job schedulers pzCheckProfileMergeKafkaAlert and pzMergeMetricsConfigPulse to run on node types RealTime, Batch or Background. These Job Schedulers are needed only for the Behavioral Merge feature which is part of Decisioning.  

These Job Schedulers are not needed if the environment is not using Decisioning but currently the application does not cater for this exclusion, and it will display an error when it detects that there is no Realtime node in the environment.   

Solution

If you are not using Decisioning, execute the following steps to disable these Job Schedulers: 

1. Log into Dev Studio 

2. In the navigation pane of Dev Studio, click Records. 

3. Expand the Technical category, and then click Activity. 

4. Open activity pzCheckForFinalConflict in private edit 

5. Navigate to the Steps tab and find Step 5. 

6. In the Label field, enter //. 

7. Navigate to Security tab and under section Restrict access, uncheck Allow invocation from browser checkbox  

8. In Dev Studio open Job Scheduler pzCheckProfileMergeKafkaAlert  

9. Click button Save as. 

10. Repeat step 8 and 9 for Job Scheduler pzMergeMetricsConfigPulse 

This issue is planned to be addressed in a future Pega Platform release.  Issues are prioritized based on impact, severity, and capacity. The specific release for the fix has not yet been determined.  This section will be updated with release details when the fix for this issue is available. 

References

 Configuring steps in an activity

Securing an activity

Managing job schedulers

PEGA0098 alert: Job scheduler failed to register for the next run

Job scheduler FAQ

Job schedulers and queue processors included with Pega Platform

pzCheckProfileMergeKafkaAlert and pzMergeMetricsConfigPulse Job schedulers