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

Cases get stuck in work basket after moving to broken queque



Cases move to a broken queue and get stuck in the work basket. Error occurs in the broken queue. However, the user is unable to identify which entry causes the error.

Error Messages

ORA-00001: unique constraint (ABC_DATA.PC_HISTORY_WORK_PK) violated 

Steps to Reproduce


Service Level Agreement (SLA) rule is configured with the activity running, upon reaching the dead line. The deadline is set to three minutes.

Root Cause

The issue is caused in multinode environments due to getCurrentTimeStampUnique.



The issue is fixed in 7.4.1 with Rule Utility Function (RUF) getCurrentTimeStampThreadUnique. 


Published 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