---
title: "High CPU usage due to missing status in SLA configuration"
canonical: "https://support.appfire.com/space/SUPPORT/326205534/High%20CPU%20usage%20due%20to%20missing%20status%20in%20SLA%20configuration"
format: markdown
---
This page explains how to resolve an error due to a missing status in the SLA configuration.

## Symptoms

- An error has shown that the status was not found for SLA configurations.

```
2024-01-23 13:07:07,694-0600 http-nio-8081-exec-261 ERROR admin.jira /rest/api/2/issue/TKT-17245 [c.s.j.p.timetosla.service.w] [Time to SLA Plugin for JIRA] Status not found for SLA Configurations needed fields, ID: 100
```

This issue is causing:

- High CPU usage

- Increased I/O reads in the database

- Overall slowness in the Jira instance

## Root cause

The error is triggered when the Time to SLA (TTS) app attempts to access a **status ID** that no longer exists in Jira (likely deleted). Despite its removal, the status ID remains referenced in one or more SLA configurations.

In this particular case, status ID 100 appears to be missing or deleted.

## How to identify affected SLA rules

To resolve the issue:

- Review all Time to SLA rules in your instance.
- Look for any rules containing unnamed statuses or statuses listed as ID numbers only (for example, 112312.x or (16300)).
- These unnamed or numeric-only statuses usually indicate deleted or missing statuses.

## Resolution

1. Remove any deleted or invalid statuses from the affected SLA configurations.
2. Save and re-index if necessary.
3. Once these references are removed, the error should no longer appear, and Jira performance should improve.