Standard Agent is not picking the item and it is in the Scheduled Status only
Hello,
I have a standard agent whose agent activity class is System-Queue-ExecutionRequest-Connect-MX (which is under the CL System-Queue-ExecutionRequest-Connect-). It is periodic (30 seconds interval) with auto-queue management
The items are saved under the CL but with a pyAttempts set to 0. They are not being processed !!
Is there a missing configuration?
Can we add a Standard Agent whose activity is under CL System-Queue-ExecutionRequest-Conect- or does it always have to be an Advanced Agent ?
Any help will be greatly appreciated :)
Thank you,
Mariane
***Moderator Edit: Vidyaranjan | Updated Categories***
Pegasystems Inc.
IN
Hi,
Can you please open the queue item and check the xml of it for the property 'pyAgentName'
If this property is null, the agent may not pick it up.
Verify if that property is populated with the agent name you have created .
Murex
LB
Hello Haritha,
Many Thanks for your reply :)
The Agent name is indeed null. How can I populate with the agent name I have created ??
Please note that I am calling a Connect-REST with execution mode to Queue whose Request Processor's queue class is: System-Queue-ExecutionRequest-Connect-MX. The Connect-REST is in charge of inserting items in the queue so I am not sure how I must specify the Agent Name.
(One additional note is that the agent activity is in the custom queue class System-Queue-ExecutionRequest-Connect-MX)
Any help will be greatly appreciated :)
Thank you,
Mariane
Virtusa IT Consulting
AE
If agentname is coming null check for stored procedure 'reservequeueitem' if this stored procedure is coming in alert logs and printing Pega0005 alert for taking much time for this agent (you can check the firsactivity column to trace the agent activity) then this is a bug, You cant request for the hotfix.
Updated: 16 Feb 2017 6:45 EST
MDCloud
CY
That's a good point, but there is a queue format issue. ExecutionRequest has different structure, queue item for standard agent should be created via Queue-For-Agent.