Skip to content

Commit bf16483

Browse files
committed
duplicate sla kpi instances
1 parent 2894c64 commit bf16483

4 files changed

Lines changed: 66 additions & 0 deletions

File tree

11.5 KB
Binary file not shown.
Lines changed: 12 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,12 @@
1+
{
2+
"Version": 1,
3+
"WorkspaceRootPath": "C:\\MarchMicrosoftDocRepo\\",
4+
"Documents": [],
5+
"DocumentGroupContainers": [
6+
{
7+
"Orientation": 0,
8+
"VerticalTabListWidth": 256,
9+
"DocumentGroups": []
10+
}
11+
]
12+
}

.vs/VSWorkspaceState.json

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
{
2+
"ExpandedNodes": [],
3+
"PreviewInSolutionExplorer": false
4+
}
Lines changed: 50 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,50 @@
1+
---
2+
title: Duplicate SLA KPI instances are being created.
3+
description: Provides a resolution for an issue where the duplicate service-level agreements (SLA) KPI instance are being created.
4+
ms.reviewer: sdas, ghoshsoham
5+
ms.author: v-heenaattar
6+
ms.date: 11/03/2025
7+
---
8+
9+
# Duplicate SLA KPI instances are being created.
10+
11+
12+
This article provides a resolution for an issue where the duplicate service-level agreements (SLA) KPI instance are being created.
13+
14+
## Symptoms:
15+
16+
- Duplicate SLA KPI instances are seen been created during update of status of slakpiinstances or duplicate slakpiinstance are created at once.
17+
18+
- Eg., When SLA is applied to a record like Case and the SLA has one slaitem created for Resolve By KPI, then when the conditions on the Case for SLA are met only one slakpiinstance for ResolveByKPI will be created. But in some cases we see duplicate slakpiinstance for ResolveByKPI been created.
19+
20+
## Cause:
21+
22+
- Custom logic implemented by custom plugins/workflows/flows/actions.
23+
24+
## Mitigation:
25+
26+
Out-of-the-box (OOB) functionality automatically creates SLA KPI instances. Hence the below customizations should be checked.
27+
28+
1. Analyze Existing Customizations on OOB flows:
29+
30+
a. Review the custom logic implemented in the SLA monitoring flow and SLA item flow.
31+
32+
b. Identify redundant triggers for creating SLA KPI instances.
33+
34+
2. Validate custom plugins and workflows:
35+
36+
a. Disable custom plugins and workflows and check if the issue is still a repro.
37+
38+
b. In this case custom plugins logic should be revisited and rectified.
39+
40+
3. Privilege Misconfiguration:
41+
42+
a. Please make sure that the prerequisites for user privileges should be met as per the SLA document here:[roles](/dynamics365/customer-service/administer/define-service-level-agreements#prerequisites)
43+
44+
4. Ordering of SLAItems :
45+
46+
a. Ordering of SLAItems in the SLA might also cause duplication of the SLA.
47+
48+
b. In this case, slaitems causing duplicate slakpiinstance should moved at the top in the sequence in the SLA.
49+
50+

0 commit comments

Comments
 (0)