Support Article
BROKEN Queue: Class Data-BatchOutPRXXX does not exist
SA-86384
Summary
The Pega Marketing 7.3.1 is installed on Pega Platform 7.3.1.
When the Pega application receives real time events, new entries are generated continuously in the broken queue and an error message displays. This occurs intermittently.
Error Messages
<?xml version="1.0"?>
<pyAttempts>2</pyAttempts>
<pxUpdateSystemID>b9cb2d6ad0f11c14d377a944e89214e7</pxUpdateSystemID>
<pxUpdateAgentName>PegaMKT-Engine:ProcessEventRun</pxUpdateAgentName>
<pyItemId>SYSTEM-QUEUE-PROGRAMEVENTS 1560402172545000A35DFA8E4DA07F1F9B6ADF6F7C722447</pyItemId>
<pyPriority>0</pyPriority>
<pxLastExecutionDateTime> </pxLastExecutionDateTime>
<pxCreateDateTime> </pxCreateDateTime>
<pyMinimumDateTimeForProcessing> </pyMinimumDateTimeForProcessing>
<pyUseApplications>true</pyUseApplications>
<pyItemStatus>Broken-Process</pyItemStatus>
<pxUpdateSystemNode>abc.com</pxUpdateSystemNode>
<pxInsName>SYSTEM-QUEUE-PROGRAMEVENTS 1560402172545000A35DFA8E4DA07F1F9B6ADF6F7C722447</pxInsName>
<pxSaveDateTime> </pxSaveDateTime>
<pyAccessGroup>MKT:MarketAdmins</pyAccessGroup>
<pyAgentName>PegaMKT-Engine:ProcessEventRun</pyAgentName>
<pyMinimumAgeForProcessing>0</pyMinimumAgeForProcessing>
<pzInsKey>SYSTEM-QUEUE-PROGRAMEVENTS SYSTEM-QUEUE-PROGRAMEVENTS 1560402172545000A35DFA8E4DA07F1F9B6ADF6F7C722447</pzInsKey>
<pyMaxAttempts>1</pyMaxAttempts>
<pxObjClass>System-Queue-ProgramEvents</pxObjClass>
<pyRetainOnSuccess>false</pyRetainOnSuccess>
<pyRetainOnFailure>true</pyRetainOnFailure>
<pySelectId>1560402172545000A35DFA8E4DA07F1F9B6ADF6F7C722447</pySelectId>
<ProgramRunId>PEGAMKT-WORK P-6</ProgramRunId>
<pzLastRunSuccessful>false</pzLastRunSuccessful>
<pzStatus>valid</pzStatus>
<pxQueueErrorDetails REPEATINGTYPE="PageList">
<rowdata REPEATINGINDEX="1">
<pxObjClass>Embed-QueueErrorDetails</pxObjClass>
<pxErrorMessage>Class Data-BatchOutPR473 does not exist</pxErrorMessage>
<pxErrorDateTime> </pxErrorDateTime>
<pyAttempt>1</pyAttempt>
<pxTraceList>[]</pxTraceList
Steps to Reproduce
- Associate a real time event with a Campaign.
- Trigger the event.
Root Cause
A defect in Pegasystems’ code or rules.
When a real-time event is triggered and the current Interaction History (IH) record category class purged (deleted from the instance), the filter in-flight logic is broken when the search for a purged class is stopped.
Resolution
Apply HFix-55560.
Tags:
Published December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.