Are any other SL rules running properly? If they are all not running properly then the problem is likely at the agent scheduler. If there are SL rules running properly, then you may want to create a temporary SL to test if it works, then replace the current non-functional one with the one that is working.

Thanks for the response.

Yes, there are other SL rules that are running correctly.

Even in my scenario, the urgency is correctly being increased as per the Initial urgency of the SLA rule. So i suppose my SLA is being picked up.

Hi Supriya,

Can you trace the agent by delaying it (ServiceLevelEvents) and see if it is failing.

Are your SLA rules based on other properties. I mean is your SLA rule property based?  Did you check the idea of delaying the execution and trying?  You can check the clipboard before execution if those properties you are using in the SLA rule have value.

Are there any security of rules preventing the exeuction. If other SLA rules are running, try changing your SLA rule to the same class and AG of those running to check if its bcoz of security.

 I am just giving pointers.  Not sure of the problem what it is with a little details here in this thread.

Hi Supriya,

  am having the same issue. Did you get any solution for this? Appreciate any insight into this. Thanks.

Hi all, When it comes to SLA debugging, the first thing I always ask people is whether the goal and deadline events made audit trail instances or not. If not, then the goal and deadline events never occurred, and it is time to figure out why. If they did, then likely the SLA being run for the event is not the same as the one you are expecting. To confirm that, you can add an SLA goal action (in addition to the missed urgency increase), and see if that action occurs or not.

Hi Supria/Ajaykumar,

 

I go with Marik reply.  Kindly check if the audit enteries were picked up for execution by the SLA agent and printed in the log or not.   that is have the goal activity just to add log-message in its first step.

1.   If the log entry is printed.  Then there is no issue with SLA but with the rules designed in the system.

 

2.  If the log entry is not picked up.  You can check the log if there is any error like

a.  Unable to execute this activity due to .....  Check if its the goal activity and whats the error message

b.  Unable to find the value of the property....  Then it may be due to the property based SLA rule doesnt have the value at runtime.

c.   If the SLA rule simply dies without any error in log, that may because the SLA queue having lot of entries and it may take days to reach this queued entry.  So check if the SLA queue is overfull

Do post your findings and issues in this thread.