SLAs not getting calculated for some HR cases despite SLAs being configured for the HR service
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
Hello
We have encountered an issue with SLAs not getting calculated for some HR cases getting created for General HR questions services.
The 7 day SLAs are configured to HR Employee Relations case (sn_hr_core_case_relations) table. We also checked that the General HR question (both HR service and Record Producer) is created on the same table. So for the HR cases created on HR Employee Relations case SLAs are getting calculated. However the highlighted HR cases are getting created on sn_hr_core_case table. As a result, SLAs are not getting calculated. Our problem is that why some HR cases are getting created on parent table instead of relations table and how can we resolve this issue?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
2 hours ago
Please refer this links, see if it helps you:
Please refer this links, see if it helps you:
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
an hour ago
Hi @shwetasg23 !!
In HRSD, the case table is decided by the HR Service configuration.
Your SLA is configured on sn_hr_core_case_relations, so it works only when cases are created on that table. Some “General HR Question” cases are getting created on the parent table sn_hr_core_case, so the SLA is not triggering.
Please check:
The Case Table field on the HR Service — it should be set to sn_hr_core_case_relations. If it is blank, the case gets created on the parent table.
Make sure there are no multiple HR Services or Record Producers mapped differently.
Verify the HR Service is correctly mapped to the Employee Relations COE.
Once the Case Table is set correctly, the SLA should work for all cases.
Mark this as Helpful if it clarifies the issue.
Accept the solution if this answers your question.
Regards,
Vaishnavi
Associate Technical Consultant
