> For the complete documentation index, see [llms.txt](https://docs.patchmypc.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.patchmypc.com/patch-my-pc-publisher/manage/configmgr-apps-tab/form-controls/refresh-cloud-product-list.md).

# Refresh Cloud Product List in Patch My PC Publisher

*Applies to: Patch My PC Publisher V3.x*

{% hint style="danger" %}
**Important**

This article has not been updated for Version 3.x. Once it has, this banner will be removed.
{% endhint %}

The **Refresh Cloud Product List** form control in Patch My PC (PMPC) Publisher refreshes the list of custom products displayed in the **All Custom Products** [product tree](/patch-my-pc-publisherv2/administration/configmgr-apps/product-tree.md). This list includes applications that were created as [Custom Apps in a Patch My PC Cloud company](https://docs.patchmypc.com/patch-my-pc-cloud/custom-apps) and synchronized to the Publisher.

The Publisher calls the Patch My PC Cloud Catalog API to retrieve the current list of supported custom products. The returned data is processed and used to update the **All Custom Products** tree on the ConfigMgr Apps tab, ensuring the console reflects any newly created, modified, or removed custom products in the cloud.

The refresh capability requires that the cloud connection is already configured and enabled on the [Cloud](/patch-my-pc-publisherv2/administration/cloud.md) tab.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.patchmypc.com/patch-my-pc-publisher/manage/configmgr-apps-tab/form-controls/refresh-cloud-product-list.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
