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

Items in Broken Queue caused by “Class <blank> does not exist”



If a child case is instantiated based on a dependency of the parent's work status, an error occurs if the dependent status is set before an initial assignment has occurred. 

Because the processing in the application is initiated by an agent on a record in system queue, there is an error on the page classifying it as “broken-queue”.

Error Messages

“Class <blank> does not exist”

Example from log (with no stack trace)
2015-04-15 09:51:57,969 [ PegaRULES-Batch-2] [ STANDARD] [ EDN:01.03.01] ( internal.access.DatabaseImpl) ERROR - Cannot open the requested instance '': class or class group "" does not exist.

Steps to Reproduce

  1. In the parent flow shown below, the status is updated to Pending-Approval as soon as the case is started.
  2. A child case is instantiated based on the status of the parent.
  3. When you test this, an error occurs in the update status activity (visible in the Tracer).

Root Cause

A defect in Pegasystems’ code or rules
There is no impact from this error under normal circumstances. In this case, because of the associated agent processing, a broken queue item was created.


Apply HFix-22161.


Published January 26, 2017 - 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