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

Timeout issue with BIX extraction



Business Information Exchange (BIX) extraction's 'Generated SQL' is going timed out with Pega 7.2.2.

Error Messages

SELECT COUNT("PC0"."pzInsKey") AS "pySummaryCount(1)" FROM PEGA_DATA.pc_InvestDepositApp_Work "PC0" WHERE ( "PC0"."pzInsKey" LIKE ? AND "PC0"."pxCommitDateTime" >= ? AND "PC0"."pxCommitDateTime" < ? ) The query has timed out.

Steps to Reproduce

1.Create a BIX extract rule on work class which is of type - 'Class Group'. So the filter condition will be generated on pzInsKey column with Like clause, instead of pxObjClass column.
2. Do not select 'Skip standard order by clause' under 'Filter Criteria' tab.
2. Have more number of work objects to get extracted.
3. Run the extract rule.
4. Check the Pega RULES/ Pega BIX logs for the above error.

Root Cause

Since there are more number of work objects and also filtering is enabled by default.


Enable 'Skip standard order by clause' under 'Filter Criteria' tab and create indexes for the work object tables columns to resolve the issue.

Published March 22, 2018 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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