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

Custom Queue Processor fails



Custom Queue Processor does not work. No status displays for the Custom Queue Processor on the Admin Studio.

Error Messages

074 [ndProcessing_Test:55] [ STANDARD] [ ] [ ] (internal.mgmt.Executable) ERROR   - Exception Unable to authorize flow execution :RULE-OBJ-FLOW PEGA-DM-DDF-WORK NEWWORK #20180713T140252.333 GMT
com.pegarules.generated.flow.ra_action_newwork_c1ead6dc9dad73d83fe2601e1f504e7b.perform( ~[?:?]
com.pega.pegarules.session.internal.mgmt.Executable.doActivity( ~[prprivate.jar:?]
com.pegarules.generated.StartFlow_080101_2298051497592355613.StartFlow08_01_01( ~[?:?]
com.pegarules.generated.StartFlow_080101_2298051497592355613.invoke( ~[?:?]
com.pega.pegarules.generation.internal.library.LibraryRuntime.resolveAndinvokeFunctionViaReflection( ~[prprivate.jar:?]
at com.pega.pegarules.generation.internal.library.LibraryRuntime.invokeLibraryRuntime( ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.mgmt.Executable.invokeLibraryRuntime( ~[prprivate.jar:?]

Steps to Reproduce

  1. Create a new Queue Processor instance
  2. Verify if the status of the Queue Processor displays as Running on the Admin Studio

Root Cause

Queue Processor is unable to move to Running status due to an issue with privilege.


Perform the following local-change: 
Update the ASYNCPROCESSOR Requestor Type with PegaRULES:AsyncProcessor role which contains the AllFlows privilege.


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