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

SLA Queue Entries not rolled back



If an exception occurs and a database rollback occurs: the SLA status ('pyItemStatus') of the item is not rolled-back, instead, the status remains as 'Now Processing'.
The item is never picked, because the SLA Agent ignores items in this status.

Error Messages

Not Applicable

Steps to Reproduce

1. Create a test flow:

Assignment A > Utility > Assignment B

2. Within the Utility: ensure a Database Rollback is generated.
3. In Assignment A , configure an SLA  time of a few minutes.
4. Run the flow, confirm that case gets really rolled back to Assignment A after encountering the Rollback generated by the Utility.
5. Wait until SLA goal time is reached, verify that the SLA is not processed.

Root Cause

A defect in Pegasystems’ code or rules.


Apply HFix-23680.


Published January 31, 2016 - 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