Support Article
PEGA0005s on System-Queue-WaitFlow Pega Marketing
SA-23468
Summary
Large number of PEGA0005 alerts associated with System-Queue-WaitFlow processing are emitted.
Error Messages
**Date and time**,100 GMT*8*PEGA0005*727*500*4e5890410ae4e227eb705b05fb86814e*NA*NA*B4795437631F956D9A20D63B2936D23C1*System*MYMKT-Work*MYMarketing:01.01*MY4879912d2854cde5e1844bfbebf8fa*N*181*B4795437631F956D9A20D63B2936D23C1*9156*PegaRULES-Batch-4*STANDARD*com.pega.pegarules.data.internal.access.DatabasePreparedStatementImpl*NA*System-Queue-WaitFlow.ProcessWaitingOfferFlows*Rule-Obj-Activity:EstablishContext*SYSTEM-QUEUE- PROCESSOFFERBATCH #20150910T223238.214 GMT Step: 34 Circum:
.
.
.
Steps to Reproduce
Set up a large custom base with High Partition count.
Root Cause
A defect in Pegasystems’ code or rules:
The query used by Wait flow processing uses "current_timestamp." The query runs slow, as there is no Index on WAITEXPIRATIONTIME and PARTITIONKEY column in Batch and Event tables.
Resolution
Apply HFix-27287.
Published August 23, 2017 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.