Question
Cognizant Technolgy Solutions
IN
Last activity: 22 Mar 2023 15:52 EDT
"Unable to find the queue processor instance in memory" error on Queue for processing
Hi All,
Created a new Queue processor in my implementation work class and queued items for it from an activity using Queue-for-processing method using the following params -
Type of Queue - Dedicated
QueueProcessor - my Q P name
Lock Using - None
Write Now - Checked
Queue current snapshot of the page - tried with both checked and unchecked
Alternate access group - none
Error that I am receiving is - "Unable to find the queue processor instance in memory"
If I run the queue processor activity as a stand alone module, it runs perfectly fine.
Can anyone share any idea on what I might be missing here?
thanks,
Arka
Pegasystems Inc.
US
Hi @Connect@Abicom,
Were you able to try "enabling include in background processing checkbox in application - advanced settings" to see if this resolved it for you as it did for @Rathnach ?
WFC
IN
@MarissaRogers Yes I did same thing, he can try it
its in Application rule - definition tab, advanced section - and that check box for background processing.
ANZ
AU
@ABHATTCHRYA Point your AsyncProcessor Requestor type access group with the correct application access group which have access to process the Dedicated queue items . By defaut it will be pointing to PRPC:AsyncProcessor
USU GmbH
DE
Did you find a solution?
We have the same error when queueing an case with Queue For Processor during an ServiceLevelEvent Standard Agent run.
The Queue For Processing Works if the User runs the process, as soon the Queue For Processing is executed in the Background Standard Agent ServiceLevelEvent, our Custom Queue Processor is not found.
I have tried to setup the PRPC:AsyncProcessor also PRPC:Batch Reqeustor type. This was not helpfull.
Coforge
IN
Issue is resolved by checking system run context.
Please verify application stack and respective ruleset versions that has updated queue processor rules.
Regards,
Aparna
Softserve Inc.
US
I recently faced this issue, even though the system runtime context had my application and correct version. Upon manually saving this, the queue processor instance started to show up on the admin studio.
The 'save' button on the top right corner of the system runtime context landing page.