Skip to main content
Solved

Issue with "Set Case SLA Action" - Timer Not Reflecting Placeholder Time

  • August 21, 2024
  • 5 replies
  • 61 views

Forum|alt.badge.img+10

I'm encountering an issue with the "Set Case SLA Action" in our system. The time captured by the Placeholder isn't being reflected correctly in the Case SLA Timer. However, when I check the View Result, the timing appears to be correct.

Has anyone else experienced this problem? If so, could you please share any solutions or workarounds that might help?

Thanks in advance!

Best answer by skadav

I am able to resolve the issue now. Thanks all.

Basically, Set Case SLA Action is setting Breach time as = "Case Creation Time - (Subtract) - SLA Breach Time"
And It sets Critical Time as = "SLA Breach Time - (Subtract) - SLA Critical Time"


Example:
If we want to set SLA Clock Timer as "15 min for SLA Breach Time" and "10min for SLA Critical Time"
Then I need to set "SLA Breach Time = 15" and "SLA Critical Time = 5"

5 replies

dnehoda
Staff
Forum|alt.badge.img+16
  • Staff
  • August 23, 2024

Hello, 

I have configured a playbook using that action and see this. 

So that would be step one.  If Im understanding you correctly, you are not seeing this 


SoarAndy
Staff
Forum|alt.badge.img+12
  • Staff
  • August 23, 2024

In a quick playbook I set some Alert context values, then used them in the SLA Actions 

I ran this playbook against a new alert, and the new SLA appeared

Note, the SLA starts from when the stage was assigned, not when the Action ran (i.e. if you set to 10 minutes, but the case is already 12 minutes old)

 


Forum|alt.badge.img+10
  • Author
  • Silver 2
  • August 23, 2024

Hello Guys,

my issue is this:

Time showing in result is not visible in clock timer. It seems clock showing some random value.

 

 


Forum|alt.badge.img+10
  • Author
  • Silver 2
  • August 23, 2024

In a quick playbook I set some Alert context values, then used them in the SLA Actions 

I ran this playbook against a new alert, and the new SLA appeared

Note, the SLA starts from when the stage was assigned, not when the Action ran (i.e. if you set to 10 minutes, but the case is already 12 minutes old)

 


Thanks Andy. This line helped "case is already 12 minutes old"


Forum|alt.badge.img+10
  • Author
  • Silver 2
  • Answer
  • August 23, 2024

I am able to resolve the issue now. Thanks all.

Basically, Set Case SLA Action is setting Breach time as = "Case Creation Time - (Subtract) - SLA Breach Time"
And It sets Critical Time as = "SLA Breach Time - (Subtract) - SLA Critical Time"


Example:
If we want to set SLA Clock Timer as "15 min for SLA Breach Time" and "10min for SLA Critical Time"
Then I need to set "SLA Breach Time = 15" and "SLA Critical Time = 5"