In my application, our end users are reporting an issue where the create a case using one of the functionalities and cases are not getting created immediately, and at times getting created at a huge delay extending to almost an hour.
This functionality uses Queue Activity method. So, we feel its a delay in the Queuing process. In order to reproduce this issue lower environment, we are getting a slight delay, say around 2-3 minutes, but not more.
If anybody has faced similar situation and can throw some lights of what exactly could be the issue in queuing and which configurations could help resolve this, it would be of immense help.
***Edited by moderator, Maryrita: moved to Product Support from Applications***
Can you please elaborate a little bit more on how to implement it. Also, want to re-iterate- we don't have any agent in this problem. We are using Queue <Activity Name> method. So, I guess, Pega internally uses some agent to process the activity in a queue similar to an agent, but I am not sure how to modify the configuration of such set up.
As a starting point, I'd suggest trying to pinpoint where the queued activity is spending the extra time. You may want to try:
Seeing if the same kind of delay occurs when the activity is run in the same requestor, rather than being queued.
If it does, you can try tracing scenario and review the trace to see where the most time was spent.
If it does not, you can try adding Log-Message steps into the activity between the existing steps, and then executing the activity via the queue method. You can use their time stamps to see which steps are taking the longest.
Once you know where the time is being spent, you can narrow your focus to see what might be causing it.
Can you provide additional information as to what happens in the queued activity? Does it need to connect to any other systems? Also, what is the value of the agent/threadpoolsize setting in your environment (prconfig or DSS)?