Last activity: 31 May 2018 11:25 EDT
Now Processing queue entries with older last execution date timestamp
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 ?