Prowler scan stuck in "Executing" state — cannot be canceled or recovered

[armanfeyzi]

Steps to Reproduce

Issue
A scan remains stuck at “Executing” (94%) since April 25, 2025, and never completes. Deleting the prowler-api pod does not resolve the issue—the scan still appears stuck in the UI after pod restart.

Steps to Reproduce

1. Deploy Prowler in namespace k8s.
2. Start a scan via UI or API.
3. Some scans complete normally, but one remains stuck in “Executing.”
4. No Kubernetes Job or scan pod is visible for this stuck scan.
5. Deleting the prowler-api pod has no effect—the scan status remains.

Actual Behavior

• Scan is stuck permanently in UI.
• No pod or job to delete.
• Restarting the pod doesn’t help.

Request

• How can we cancel or recover from stuck scans?
• Can old scan states be purged from the database or UI?
• Is there a timeout or retry mechanism for long-running scans?

Expected behavior

• Scan should complete or fail with an error.
• If stuck, it should be cancelable.
• Restarting prowler-api should clean up orphaned/stuck scans.

Actual Result with Screenshots or Logs

![Stuck scan at 94%]

How did you install Prowler?

Cloning the repository from github.com (git clone)

Environment Resource

• Prowler : 5.7.2
• Kubernetes: EKS v1.31

OS used

Linux - GNU/Linux

Prowler version

5.7.2

Pip version

pip 25.1.1 from /home/prowler/.local/lib/python3.12/site-packages/pip (python 3.12)

Context

No response

[pedrooot]

Hey! First of all, thanks for the detailed report, it helps a lot having all of this information.

To resolve this we can follow two types of paths:

• Provider path -> Delete the provider, take into account that with this action you'll delete old scans too.
• DB path -> Go in the database and remove this scan, this one won't delete old scans from this provider.

Tell me if that works for you.