Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Slow query on Event tables



Performance degrades when querying MKT_EVENT_P711 and MKT_EVENT_P713 from the DF_Wait dataflow.

When the Outbound campaign's (PR-xxx) dataflow is running and a DF_Wait dataflow starts, the dataflow nodes consume 100% CPU and the outbound Program Run (PR) performance degrades. Additionally, the DF_wait dataflow takes more than 20 minutes to process the records (1 to 10).

Error Messages

Not Applicable

Steps to Reproduce

Run an event Campaign.

Root Cause

A defect in Pegasystems’ code or rules.
The DF_Wait dataflow generates queries with the Where clause on CustomerID because the Event dataset (for the campaign output table) is keyed on the CustomerID property. However, there are no indexes on the CustomerID column when the EVENT table is created.


Apply HFix-53539.
Suggest Edit

Published August 19, 2019 - Updated December 2, 2021

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us