# Recovery request has negative timestamp

**Error**

The logs indicate a recovery request with a timestamp value of After=-62135582400000.

**Applies to:**

UOF SDK .Net (both versions)

**Symptoms**

Users may observe log entries like:

```
2023-05-15 03:38:51,533     INFO     46     ProducerRecoveryManager     Producer=3: Recovery operation started. Current status=NotStarted, After=-62135582400000.
```

Why It Happens

When a user fails to set a custom timestamp before opening the feed, the *After* timestamp defaults to *DateTime.MinValue*, which suggests a full odds recovery is required. This behavior is accurate, despite the misleading log entry.

From the logs:

```
2023-05-24 11:05:07,178     INFO     19     ProducerRecoveryManager     Producer=1: Recovery operation started. Current status=NotStarted, After=-62135582400000.
2023-05-24 11:05:06,746     INFO     19     Id:273589213 Posting url: https://global.api.betradar.com/v1/liveodds/recovery/initiate_request?request_id=273589212&node_id=501
```

Although the log shows a negative After value (indicating no specific After value is set), the recovery request is executed correctly without this parameter.

**Resolution**

Updating to SDK .Net Core v2.0.0 or later resolves this issue by correcting the log entry behavior.

**Status**

No further action is necessary as the recovery request functionality remains unaffected despite the log message display.


---

# 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/recovery-request-has-negative-timestamp.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.