## TL;DR

Per Prisma Cloud guidance: the Agentless scan column plus console logs are the first place to look when scans stall. In the console, the "Agentless scan" column gives a brief per-account description of what is wrong.

## Steps

1. Per Prisma Cloud guidance: the Agentless scan column plus console logs are the first place to look when scans stall.

2. In the console, the "Agentless scan" column gives a brief per-account description of what is wrong.

## When to use

You are seeing this: Per Prisma Cloud guidance: the Agentless scan column plus console logs are the first place to look when scans stall. Use this skill when you run into "Prisma Cloud agentless scan not producing results - check the Agentless scan column and console logs".

## When not to use

If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.

## Versions

No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.

## Why this happens

The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
