SLAs Cancelling

[scottjus82]

Hi all,

I assure you I do work some issues out myself!!

We have an issue in which SLA's are canceling rather than completing and I cant work out why. I have the following examples;

A ticket with two SLA's one completes and one cancels

A ticket with the same SLA as cancelled above completing

A ticket with two SLA's completing fine.

The time stamps shows it cancels on an action (re-assignemnt, state change) however the same changes have no effect in other tickets.

I have created a couple of test SLAs that kick off from each other based on the team they assign to and that flows correctly. The first starts, when reasigned it completes and the second starts when re-assigned it completes. I seem to be running around in circles trying to understand what causes an SLA to cancel on one ticket but complete on the other under what seams to be the same condition.

I am not sure if I have explained the above correctly. Let me know if you need any further info.

Regards

[Pradeep Sharma]

Hi Steve,

The same thing happend with me earlier and the main culprit was the business rule which I have created for   "state" field.

I would request you to check all the BR on your table.

NOTE: For me it worked by simply changing the new BR from before insert to after insert.

I hope this helps

Thanks

Pradeep Sharma

[raju35]

Hi All,

We have an issue in which SLA's are canceling rather than completing and I can't work out why in our production instance. I have the following example;

A ticket with three SLA is showing as cancelled but not showing Achieved & complete

And please find the attachment of the SLA Definition screen shot as well as Incident SLA cancellation screen shot.

I would request you all are there any Business Rule problem. If so please let me know how to check and change that

Regards,

Madhu

[solutioningnow · Accepted solution]

Hi Steve,

Thats an issue that we identified also while defining sla's for one of our clients.

Problem: whenever an SLA was attached to an incident and if we move the incident to any pending state value, the SLA attached to it gets cancelled. After investigating a bit what we identified was, the STATE field which was available in the start condition i.e. State == New was also available in Pending condition STATE = Pending || Waiting || XYZ.

Observation: What we have observed is that whenever an SLA having state field both in start and paused condition, whenever the pause condition is satisified it doesn't match the start condition and thats why it cancels out the SLA.

Not sure how much of this information could be helpful, but would request you to change the start condition and pause condition for once and test whether the issue persists or not, i.e try with some differend field for pause for testing perspective.

Please mark answer as correct/helpful, if it was really helpful 🙂

Regards,

Solutioner

Enhance Knowledge NOW@ www.solutioningnow.com

http://www.solutioningnow.com/

[Subhajit1]

On Aspen, exactly this reason causes stops you when you are trying to make OLAs, where an OLA record get attached when a Ticket is assigned to a Particular Group, and we are trying to Pause the OLA when the Ticket moves away from the Group.