# QP Exception

**URL:** <https://forums.pega.com/t/qp-exception/13646>\
**Category:** General\
**Created:** [October 1, 2026, 1:21pm UTC](https://forums.pega.com/t/qp-exception/13646 "2026-10-01T13:21:08Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Mike\_Helene](https://avatars.discourse-cdn.com/v4/letter/m/3da27b/32.png) [@Mike\_Helene](https://forums.pega.com/u/Mike_Helene)\
**Post date:** [October 1, 2026, 1:21pm UTC](https://forums.pega.com/t/qp-exception/13646/1 "2026-10-01T13:21:08Z")

</div>

![image](https://pega1.discourse-cdn.com/pega/original/3X/a/c/ac4e3f6a05b62c9432c5bdbe10dbe029b2b422bf.png)

 ![image](https://pega1.discourse-cdn.com/pega/original/3X/b/c/bc6b2220d72a504374180d0abf817169b93df331.png)

while running the SLA, we encountered this error. Not sure what its looking for as the pzinskey is available at pyWorkPage and even at newAssignPage. Anyone familiar with this issue?

---

<div class="post-metadata">

**Author:** ![gudip](https://avatars.discourse-cdn.com/v4/letter/g/9fc348/32.png) [@gudip](https://forums.pega.com/u/gudip)\
**Post date:** [October 1, 2026, 2:27pm UTC](https://forums.pega.com/t/qp-exception/13646/2 "2026-10-01T14:27:59Z")

</div>

Hi,

When the SLA is trying to run, are the assignments still active or have they progressed in the flow?

---

<div class="post-metadata">

**Author:** ![Mike\_Helene](https://avatars.discourse-cdn.com/v4/letter/m/3da27b/32.png) [@Mike\_Helene](https://forums.pega.com/u/Mike_Helene)\
**Post date:** [October 2, 2026, 1:56am UTC](https://forums.pega.com/t/qp-exception/13646/3 "2026-10-02T01:56:23Z")

</div>

assignments were still active. we only progressed them to stop the SLA from bombarding the queue.

---

<div class="post-metadata">

**Author:** ![BhanuPrasanthT1](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/bhanuprasantht1/32/22716_2.png) [@BhanuPrasanthT1](https://forums.pega.com/u/BhanuPrasanthT1)\
**Post date:** [October 2, 2026, 8:20am UTC](https://forums.pega.com/t/qp-exception/13646/4 "2026-10-02T08:20:16Z")

</div>

can you share more screen shots on the issue on the tracer

---

<div class="post-metadata">

**Author:** ![Mr.Muppadi\_Akhil](https://yyz2.discourse-cdn.com/pega/user_avatar/forums.pega.com/mr.muppadi_akhil/32/23249_2.png) [@Mr.Muppadi\_Akhil](https://forums.pega.com/u/Mr.Muppadi_Akhil)\
**Post date:** [October 2, 2026, 9:22am UTC](https://forums.pega.com/t/qp-exception/13646/5 "2026-10-02T09:22:02Z")

</div>

@Mike_Helene

1. Queue Processor context problem  
Queue Processors don’t run in the same thread context as the user’s session. If the activity relies on a top-level page name that isn’t mapped properly in the Queue Processor’s activity definition, or on step page parameters passed in dynamically, the engine ends up with an empty step page. That usually means the page it’s looking for simply isn’t there when the step runs.

2. missing on the step page (pzInskey)  
pyWorkPage or newAssignPage may have the key, but that doesn’t help if the step doing the database work an (Obj-Open-By-Handle, or an automated step that commits the SLA) points at a different page. If that page is a temp page or a parameter page that was never populated, pzInsKey is blank there, and the call fails.