> For the complete documentation index, see [llms.txt](https://docs.sportradar.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sportradar.com/uof/error-handling/error-catalogue/retrieved-market-descriptor-is-missing-outcome.md).

# Retrieved market descriptor is missing outcome

**Error**

Customers are encountering errors when attempting to retrieve names for variant market outcomes.

**Applies to**

UOF SDK - All versions

**Symptoms**

When requesting the market outcome name, users receive the exception "Retrieved market descriptor is missing outcome." If the ExceptionHandlingStrategy is set to Catch, the method will return a null result, and this message will only be visible in logs, such as:

```sh
2023-04-28 11:24:24,421 [WARN ] [uf-sdk-27325-1] [uf-sdk-27325-1-amqp-t-1] [c.s.u.s.i.m.NameProviderImpl] - An error occurred while generating the name for event=
[StageImpl{id=sr:stage:1052161, locales=[fr, en, es, zht, nl, de, pt]} ], market=[ MarketId=559 Specifiers=[\{variant}=\{pre:markettext:190371}] 
OutcomeId=pre:outcometext:24955559] Locale=[fr]]. Additional message: Retrieved market descriptor is missing outcome.
```

**Resolution**

Stale data may be sourced from the API itself or from the cached variant market description within the SDK. To address this, users can delete the cached data to ensure the latest information is retrieved from the API (use: MarketDescriptionManager.deleteVariantMarketDescriptionFromCache()). Additionally, it's recommended to review REST logs to confirm when the variant was last fetched, what was actually returned from the API side, and compare it with the expected market outcomes based on the feed message. This involves comparing the market structure in a feed message (from traffic-logs) with the cached market description in the SDK (from rest-logs) to identify any inconsistencies.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://docs.sportradar.com/uof/error-handling/error-catalogue/retrieved-market-descriptor-is-missing-outcome.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.