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

Errors on queueing emails to an agent



Errors display on Admin Studio after queueing emails to an agent.

Error Messages

427 [ PegaRULES-Batch-92] [STANDARD] [ ] [RuleSEt:] (ernal.async.BatchRequestorTask) ERROR - Batch activity "Data-Corr-.Send" threw: You are not authorized to open instance SYSTEM-QUEUE-DEFAULTENTRY SYSTEM-QUEUE-DEFAULTENTRY 1571154093003000WEB-I-03F446D35FCED97F3: code: <none> SQLState: <none> Message: <none>
com.pega.pegarules.session.internal.async.agent.QueueManagerImpl$ ~[prprivate-session.jar:?]
com.pega.pegarules.session.internal.async.agent.QueueManagerImpl$ ~[prprivate-session.jar:?]
at com.pega.pegarules.session.internal.async.agent.QueueProcessor.execute( ~[prprivate-session.jar:?]
at ~[prprivate-session.jar:?]
com.pega.pegarules.session.internal.PRSessionProviderImpl.performTargetActionWithLock( ~[prprivate-session.jar:?]
com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked( ~[prprivate-session.jar:?]
com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked( ~[prprivate-session.jar:?] ~[prprivate-session.jar:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker( [?:]
at java.util.concurrent.ThreadPoolExecutor$Worker.r127.0.0.1n( [?:
at [?:]
Caused by: You are not authorized to open instance SYSTEM-QUEUE-DEFAULTENTRY SYSTEM-QUEUE-DEFAULTENTRY 1571154093003000WEB-I-03F446D35FCED97F3 ~[prpublic.jar:?]
com.pega.pegarules.session.internal.async.agent.QueueManagerImpl$ ~[prprivate-session.jar:?]

Steps to Reproduce

  1. Log in to the Dev portal and switch to Admin Studio
  2. Navigate to Agent Queues
  3. Select Scheduled Category
  4. Select System-Queue-DefaultEntry
  5. Select an entry on the queue of type SendCorr. Errors occur

Root Cause

Batch Requestor Type does not have the correct access group configured.


Perform the following local-change:
Update the Batch Requestor Type to use the correct access group for the environment.



Published July 23, 2020 - Updated December 2, 2021

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