Question7Replies358Views Suranjith Member since 2015 8 posts Self Employed Posted: January 11, 2018Last activity: February 15, 2018 Closed Solved Routing doesn't work properly when SLA rule added to the assignment.An assignment has configured as route to a Work Basket. When a Service Level Agreement (SLA) rule added to same assignment routing doesn't work properly.If removed SLA reference, it works fine. Is there a solution for this? Case Management ×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: 2 years agoCarissaW_GCS PEGA replied to SuranjithWhat is the error message that occurs? Posted: 2 years agoSuranjith Self Employed replied to SuranjithThis issue is on: Pega Platform v7.1.9 Pega Customer Service for Communication v7.1.4 Mozilla Firefox Quantum v57.0 Microsoft Windows 10 Posted: 2 years agoSudhakarReddy PEGA replied to SuranjithHi, It seems to there is a issue with workbasket rule, please revalidate your application once.. Posted: 2 years agoSuranjith Self Employed replied to SuranjithCarissaW_GCS, There is no error message in UI. Case is getting routed to workgroup manager. SudhakarReddy, If the SLA rule is removed for assignment in flow rule, routing works properly. Posted: 2 years agoAsif Hasan PEGA replied to SuranjithIs the SLA configuration correct? Verify that, activity configured in SLA is reporting some problem. It could be value to the property isn't passing correctly or any other generic activity error. Please run the use-case and share the tracer capturing it. Also PegaRULES log file for initial investigation. Posted: 2 years agoSuranjith Self Employed replied to Asif Hasan@Asif_Hasan, I dont have access to a 7.1.9 environment now to get logs. The issue was there even with a newly created SLA rule with no actions defined. Accepted Solution Posted: 2 years agoSuranjith Self Employed replied to SuranjithUpgrade to Pega 7.3.1 resolved the issue.