> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/application-security/code-to-cloud/code-to-cloud/references/reference-d-recommended-actions-by-view-and-stage.md).

# Reference D: Recommended actions by view and stage

This appendix lists the recommended-action catalog surfaced by the Coverage dashboard's Insights region, by view and stage.

## Code-2-Cloud artifact

| Stage            | Insight title                                    | Action label         | Action button                               |
| ---------------- | ------------------------------------------------ | -------------------- | ------------------------------------------- |
| Code → Build     | VCS Repositories without traces to build         | Onboarding suggested | Onboard CI/CD instances → Data Sources      |
| Build → Deploy   | VCS Repositories without traces to deploy        | Onboarding suggested | Onboard Container Registries → Data Sources |
| Deploy → Runtime | VCS Repositories reaching Deploy and not Runtime | Onboarding suggested | Onboard Cloud Accounts → Data Sources       |

## Code-2-Cloud infrastructure

| Stage          | Insight title                                             | Action label         | Action button                                                   |
| -------------- | --------------------------------------------------------- | -------------------- | --------------------------------------------------------------- |
| Code → Runtime | IaC resources without YOR tag cannot be traced to runtime | Tagging Needed       | No one-click action — apply YOR via the tagging bot             |
| Code → Runtime | IaC resources with YOR tag not traced to runtime          | Onboarding suggested | Onboard Cloud Accounts → Data Sources                           |
| Code → Runtime | Cloud assets without YOR tag can be tagged manually       | Tagging Needed       | No one-click action — apply YOR manually or via the tagging bot |

## Cloud-2-Code artifact

| Stage            | Insight title                                                    | Action label         | Action button                 |
| ---------------- | ---------------------------------------------------------------- | -------------------- | ----------------------------- |
| Runtime → Deploy | Runtime Container Images not traced to Deploy                    | Onboarding suggested | Onboard Container Registries  |
| Deploy → Build   | Runtime Container Images not traced from Deploy to Build         | Onboarding suggested | Onboard CI/CD instances       |
| Runtime → Build  | Runtime VM Instances not traced to Build                         | Onboarding suggested | Onboard CI/CD instances       |
| Build → Code     | Runtime Images/VM Instances traced to pipelines but not to repos | Onboarding suggested | Onboard VCS Organization/repo |

## Cloud-2-Code infrastructure

| Stage          | Insight title                                                       | Action label   | Action button                                                   |
| -------------- | ------------------------------------------------------------------- | -------------- | --------------------------------------------------------------- |
| Runtime → Code | Cloud assets without YOR tag cannot be traced to their IaC resource | Tagging Needed | No one-click action — apply YOR manually or via the tagging bot |

> **Note:** Recommended actions in this release follow a naive heuristic — the dashboard cannot guarantee that executing a recommendation will improve coverage, only that the recommendation addresses an observed gap.


---

# 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://cortex-docs.paloaltonetworks.com/application-security/code-to-cloud/code-to-cloud/references/reference-d-recommended-actions-by-view-and-stage.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.