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

BIX sends same record in two different feeds



A script runs automatically on a schedule. Sometimes, cases with the same updated time stamp is extracted in 2 different runs. Extraction is broken into 4 to 6 hour time intervals that are run throughout the day.

015-03-18 00:16:38,064 [ main] [ ] ( internal.access.ExtractImpl) DEBUG - sql statement is: SELECT pzPVStream FROM PC_WORK WHERE pxObjClass like ? AND (( pxCreateDateTime >= ? AND pxCreateDateTime <= ? ) OR ( pxUpdateDateTime >= ? AND pxUpdateDateTime <= ? ))  ORDER BY pzInsKey

Error Messages

Not Applicable

Steps to Reproduce

Run a BIX report with a filter using -d/-D and -u/-U with start and end time values such as, from midnight to 4 am and 4 am to 8 am. This results in an extraction of any Work Object (WO) which was created or updated during the time specified.

Root Cause

The root cause of this problem is a defect in customer application code/rules. The reason for duplicate issue is because the extraction periods overlap, the end window time of one period and the start window time of the next are the same time.  


This issue is resolved by making the following change to the operating environment: 

1. Change the time ranges and update them so they do not overlap
2. Set the endtime to be 5 minutes before the time of extraction, for example, at 8 am run an extraction from 3:56.00 to 7:55.59, at noon run extraction from 7:56.00 to 11:55.59.

Published June 12, 2015 - 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