> 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/cortex-cloud-posture-management/code-to-cloud/code-to-cloud/troubleshooting.md). # Troubleshooting If the Code-to-Cloud lineage is incomplete, one or more specific signals are missing. Use the following table to diagnose and resolve common lineage gaps. | Symptom | Likely cause | Resolution | | ----------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------- | | IaC resources show as untraced despite being scanned | Missing YOR tags. IaC resources without tags cannot be mapped to runtime | The system prompts tagging for these resources. See Workflow 3: Enabling Infrastructure Lineage via YOR | | Repository shows no trace beyond the Code stage | Missing pipeline integration. If a pipeline integration is missing, the link between code and build artifacts breaks | Onboard the relevant CI/CD data source via the **Onboard Pipeline** call-to-action or the Coverage dashboard's **Onboard CI/CD instances** recommended action | | Pipeline is integrated but the repository still shows as untraced | Inactive pipeline. Lineage is generated during pipeline runs; an integrated but never-run pipeline produces no lineage | Trigger a build to generate the necessary artifacts and establish the connection | | IaC resources are tagged but still show as untraced | The matching cloud asset has not been discovered — the cloud account may not be onboarded | Onboard the missing cloud account via the **Onboard Cloud Accounts** recommended action | | A recently onboarded repository shows as untraced | Lineage is calculated by the periodic tracing job; a newly onboarded repository shows `Code-2-Cloud = NULL` (treated as untraced) until the next tracing run completes | Wait for the next tracing-job cycle. No action required | | Empty-state or troubleshooting guidance is not visible | Empty-state messages and troubleshooting guidance for missing lineage are only visible to users with an active license | Confirm the Cortex Cloud license is active and includes the required ASPM/AppSec entitlements | | Coverage % does not match the count of traced repositories | The Coverage % depends on the **Include not-onboarded repositories** and **Reach runtime instead of registry** configuration toggles, both of which change the calculation without changing the absolute traced count | Review the toggle settings. See Reference B: Coverage % calculation and configuration toggles | | Coverage dashboard filters do not scope past one lineage hop | The dashboard supports single-hop filters only in this release (for example, a filter scoping repositories that reach a specific pipeline instance is not supported) | Use the single-hop filters available for the current view, or pivot to the affected UAI table directly | | A recommended action has no action button | Recommendations labeled `Tagging Needed` or `Lineage termination` (assets that legitimately cannot be traced further) currently have no one-click action | Use the deep link to the affected assets and apply the remediation manually through the tagging bot or manual cloud-resource tagging | --- # 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/cortex-cloud-posture-management/code-to-cloud/code-to-cloud/troubleshooting.md?ask=&goal= ``` `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.