---
title: "Data within Time to SLA gadgets is missing or inconsistent"
canonical: "https://support.appfire.com/space/TTS/49742038/Data%20within%20Time%20to%20SLA%20gadgets%20is%20missing%20or%20inconsistent"
format: markdown
---
> Macro (aura-html)

## <span style="color: #000000">Problem</span>

<span style="color: #000000">Time to SLA gadgets don’t display any information.</span>  
<span style="color: #000000">**OR**</span>  
<span style="color: #000000">Time to SLA gadgets display incorrect information.</span>

## <span style="color: #000000">Diagnosis</span>

<span style="color: #000000">With Time to SLA version 9.4, all SLA gadgets switched to Lucene-backed indexed calculation mechanisms, which brought serious performance improvements. </span>

<span style="color: #000000">Sometimes those indexes get corrupted, and as a result, Time to SLA gadgets might create inconsistent results.</span>

> ℹ️ <span style="color: #000000">SLA Lucene indexes were introduced in the TTS 9.0 version along with the new slaFunction feature, which also utilizes those indexes. </span>

## <span style="color: #000000">Possible Causes</span>

<span style="color: #000000">There are two reasons why SLA indices might become inconsistent:</span>

1. <span style="color: #000000">**SLA data for some issues are missing:**</span>  
<span style="color: #000000">This is possible if you have created a new SLA contract but did not execute recalculation for existing issues.</span>
2. <span style="color: #000000">**SLA data exists but is somehow not indexed properly:**</span>  
:light_bulb_on:<span style="color: #000000"> If you have not performed a system-wide re-indexing after upgrading TTS 9.0 version then there is a very high chance that you suffer from this.</span>

## <span style="color: #000000">Solutions</span>

<span style="color: #000000">First, you have to understand which one of the possible causes fits your problem. The easiest way to find out is to browse some issues and check any missing SLAs. </span>

<span style="color: #000000">**If there are no missing SLAs on issues**</span>

<span style="color: #000000">That means SLA data is intact, but Lucene indexes are corrupted.</span>  
<span style="color: #000000">Execute a system-wide or project-wide re-indexing and check the results again. Background indexing is enough for this task.</span>

<span style="color: #000000">**If there are missing SLAs on issues**</span><span style="color: #000000"> </span>  
<span style="color: #000000">Then it means that the problem is rooted in the actual SLA data.</span>  
<span style="color: #000000">Go to </span><span style="color: #000000">**Time to SLA**</span><span style="color: #000000">* *</span><span style="color: #000000">></span><span style="color: #000000">*** ***</span><span style="color: #000000">**SLA**</span><span style="color: #000000">* for existing issues *</span><span style="color: #000000">and execute a system-wide SLA regeneration.</span>

> ℹ️ <span style="color: #000000">This solution also covers the first solution since SLA regeneration also indexes issues, but beware that SLA regeneration takes much longer than simple re-indexing.</span>