> For the complete documentation index, see [llms.txt](https://docs.limio.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.limio.com/salesforce/support/troubleshooting/offers-missing-from-catalog.md).

# Offers Missing from the Offer Catalog

Limio for Salesforce shows published offers and add-ons only. An offer that exists in the Limio Catalog, but that has no published version, does not appear in the Offer Catalog in any flow.

## Make sure that the offer is published

1. Open the offer in Limio, from the **Offers** tab.
2. Read the status next to the offer name.

| Status                  | What the agent sees                                                      |
| ----------------------- | ------------------------------------------------------------------------ |
| **Published**           | The offer is available in the Offer Catalog.                             |
| **Draft**               | The offer has no published version. The Offer Catalog does not show it.  |
| **Unpublished Changes** | The Offer Catalog shows the previous version, not your most recent edit. |

3. If the status is **Draft** or **Unpublished Changes**, click **Publish**.

The offer is available to agents immediately. A page rebuild is not necessary. For the full detail on versions, see [Manage Versions with Publish](https://docs.limio.com/product/pricing/how-to-manage-offers-and-add-ons-versions-with-publish).

## Other causes

If the offer is published and agents still cannot find it, examine these causes.

* **A filtering rule hides the offer.** The Offer Catalog pre-loads filters for each action. See [Offer Filtering Rules](/salesforce/setting-up/filtering-rules.md).
* **The Named Credentials expired.** In this case no offers at all appear, and the developer console shows 401 errors. See [Refresh Named Credentials](/salesforce/support/troubleshooting/refresh-credentials.md).


---

# 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.limio.com/salesforce/support/troubleshooting/offers-missing-from-catalog.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.