Could you please confirm which type of queue processor (Dedicated or Standard) you are using at your end. If the configured one is a dedicated Queue Processor, it will process the request at the specified time. Please trace the queue processor with the trace option in the admin-studio which helps to find the root cause.
Thanks for your response. Am using the Dedicated Queue processor. Whole issue is the Queue processor itself is "NOT" showing in running status in Admin Studio. When i click on three vertical dots and click on "View Data Flow" it says "Empty Work Item Handle".
Not sure, whether we need to do anything after the creating the dedicated queue processor in order to create the corresponding data flow object.
Changed the AG in the AsyncProcessor to make the Dedicated queue processor accessible. Any help would be much appreciated.
If it is not showing up in the admin studio under the Queue Processor, it means we are pointing to the wrong Access group in the ASYNCProcessor. If we point to the correct or our Application access group it should show up in running state.
Thank you for suggestion. If pega platform contains only one application, it works. However, if a lot applications that have different access groups running in the pega platform, this time only queue processors that are part of an application whose access group selected under Requestor Type rule works others failed.
What is the best approach to configure Requestor Type rule if pega platform includes a lot of different applications?
If multiple applications are built on a single application then create an Access Group with that application required version and specify the Access Group in the Async Requestor Type then create the Queue processors in the Built on Application Rule Set.
Second approach is : There is one more option which is Starting Rule Sets and Starting Roles. Here create a separate rule set and and specify relevant Roles for the Queue Processor. Then create the queue processor in that rule set and specify that rule set in all the applications. This might work but this approach is deprecated for latest developments.