Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Jagannath Rajagopalan (JagannathR8869) DXC Technology
DXC Technology
BE
JagannathR8869 Member since 2016 43 posts
DXC Technology
Posted: May 28, 2018
Last activity: May 31, 2018
Posted: 28 May 2018 9:24 EDT
Last activity: 31 May 2018 11:25 EDT
Closed

Now Processing queue entries with older last execution date timestamp

Dears,

In pr_sys_queues_sla, we have a lot of Now-Processing status entries of agent Pega-ProCom:ServiceLevelEvents ,

which have an old last execution timestamp.

Their max attempts is 1 and current attempt is 0. Further they all have crossed their minimumdatetimeforoprocessing.

a.) Why these are not moving to broken-process by Pega OOTB.

b.) Will these entries though older execution timestamp still hold on to db connections and have an alive thread ?

regards,

Jagan

To see attachments, please log in.
Low-Code App Development System Administration

Posted: 6 years ago
Posted: 31 May 2018 10:22 EDT
Carissa Wenhardt (CarissaW_GCS) PEGA Senior Principal Engineer, Technical Support, Industry Apps
Pegasystems Inc.
US
  • What version are you using and what type of SLA is being processed (overall SLA, assignment level, stage level, etc)?
  • Do you see any errors in the logs around the time the entry moved to Now-Processing?
  • When looking at the times of the queue entry going to Now-Processing and the history on the work objects, do you see any patterns or similarities to help identify what may be causing the issue?
To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center 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