> 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-cloud/troubleshoot/dependencies/why-is-an-app-not-shown-in-the-app-dependencies-dropdown-in-cloud.md).

# Why is an app not shown in the “App Dependencies” dropdown in Cloud?

*Applies to: Patch My PC Cloud*

### SYMPTOMS

I am trying to use the *App Dependencies* feature of Patch My PC (PMPC) Cloud, but when I click on the **App Dependencies** dropdown, I do not see the app I need to ensure is installed on the device before the app I am trying to deploy.

<figure><img src="https://3773699522-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MX7dvS0r_4fc0AikgJS%2Fuploads%2FYsmTaSJkQF913pSvwYa8%2Fimage.png?alt=media&amp;token=804b51a0-0a1d-4275-952a-112b2e816df1" alt="Required app missing from the “App Dependencies” dropdown"><figcaption></figcaption></figure>

### CAUSE

This problem can be caused if the app you are trying to create the dependency with (i.e., the one that needs to be installed before the app you are trying to deploy) has:

* not already been deployed
* not been deployed successfully. Only apps with a Success status will be shown
* only Update Only or Uninstall assignments.

### RESOLUTION

To resolve this issue, ensure that the app you are trying to create the dependency with (i.e., the one that needs to be installed before the app you are trying to deploy) has:

* Been deployed successfully.
* Has at least Available or Required assignment.


---

# 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-cloud/troubleshoot/dependencies/why-is-an-app-not-shown-in-the-app-dependencies-dropdown-in-cloud.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.