Question 1 Replies 90 Views × Close popover Jagannath Rajagopalan (JagannathR8869) DXC Technology DXC Technology BE View Profile Send Message 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 Low-Code App Development System Administration × Close popover Facebook Twitter Linkedin Email Copy Link Copied! Moderation Team has archived post, learn more × Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question. Posted: 2 years ago Posted: 31 May 2018 10:22 EDT × Close popover Carissa Wenhardt (CarissaW_GCS) PEGA Principal Software Solutions Engineer Pegasystems Inc. US View Profile Send Message CarissaW_GCS PEGA replied to JagannathR8869 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?