Question5Replies121Views shashikalaReddy Member since 2014 20 posts United Health Group Posted: 1 year agoLast activity: 1 year ago Closed OverAllSLA records in PR_sys_queue_SLAmy application have lot of 'Scheduled' instances since 1 year. 90% of them are of OverAllSLA. If the workobject is resolved, should not OverALLSLA deletes from pr_sys_queue_sla? we have written activity to clear old instances for now. please helpPega - 7.1.6 version Low-Code App Development Data Integration Java and Activities ×Close popoverFacebookTwitterLinkedinEmail Copy Link Copied! Moderation Team has archived post 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: 1 year agoMarcLasserre_GCS PEGA replied to shashikalaReddyHello, Can you check your configuration with the following article: https://community.pega.com/support/support-articles/overallsla-assignme… Not the same version but the mechanism should be the same anyway. Posted: 1 year agoshashikalaReddy United Health Group replied to MarcLasserre_GCSThanks for the quick reply. but we are using updatestatus activity every where. Posted: 1 year agoMarcLasserre_GCS PEGA replied to shashikalaReddyRight, So you are still working with Out-Of-The-Box activity "UpdateStatus" as well as Out-Of-the-Box flow "OverallSLA" correct? Is it an issue you having in all environments? Posted: 1 year agoshashikalaReddy United Health Group replied to MarcLasserre_GCSyes and in lower environment this is working fine. Posted: 1 year agoMarcLasserre_GCS PEGA replied to shashikalaReddyOk, can you trace on both environments and check what could be different maybe? I would first verify if the expected ticket is triggered correctly and of course if OverallSLA flow is resume correctly.