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”.
“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
- In the parent flow shown below, the status is updated to Pending-Approval as soon as the case is started.
- A child case is instantiated based on the status of the parent.
- When you test this, an error occurs in the update status activity (visible in the Tracer).
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.
0% found this useful