# Missing Alives

**Error Description**

The log message indicates an issue with the health and connectivity of a producer within the Unified Odds Feed (UOF) SDK. It indicates that the producer has been flagged as "DOWN" due to an "AliveIntervalViolation." This violation occurred because no subscribed alive message was received from the producer within the expected time frame (20 seconds), which is the longest period of inactivity observed.

In short, a specific producer within the Unified Odds Feed SDK did not send an expected alive message within the defined time frame.

{% tabs %}
{% tab title="Java" %}

```sh
2024-02-21 16:14:10,253 [WARN ] [] [uf-sdk-35952-2-rm-t-0] [com.sportradar.unifiedodds.sdk.impl.recovery.RecoveryManagerImpl] - ProducerDown:AliveIntervalViolation -> No subscribed alive received in 20s (longest inactivity interval), flagging producer as DOWN [Producer[1 LO]]
```

{% endtab %}

{% tab title=".Net" %}

```sh
2024-03-27 00:00:08,124 WARN   [63]   Sportradar.OddsFeed.SDK.Api.Internal.Managers.ProducerRecoveryManager   Producer id=4: alive violation detected. Recovery will be done on next system alive.
```

{% endtab %}
{% endtabs %}

**Applies to**

Unified Odds Feed (UOF) SDK - all versions

**Symptoms**

The UOF SDK performs internal periodic checks (every 10 seconds) to monitor the receipt of alive messages from each producer. If no alive message is received within the configured InactivitySeconds timeout (default 20 seconds), it triggers a ProducerDown event. The Java SDK additionally specifies an AliveIntervalViolation as the reason for the ProducerDown event. In such cases, customers are advised to stop betting on markets associated with the affected producer.

**Resolution**

* If alive violations occur across multiple producers, it could indicate a broader connection issue such as slow internet or network problems.
* If the issue is specific to a particular producer ID, verify the health and connectivity status of that producer to address the problem effectively.

<br>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sportradar.com/uof/error-handling/error-catalogue/missing-alives.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.