When an image digest referenced by a workload is no longer present in the container registry, RHACS continues attempting re-scans that fail (e.g., 404 errors).

Currently, there is no clear status indicating that the image is unavailable in the registry.

When an image is not present in the registry, RHACS should:

• Clearly indicate this state in the UI (e.g., “Image not found in registry”)

• Avoid unnecessary repeated re-scan attempts that result in continuous 404 failures

• Indicate that running workloads are using images that are no longer available in the registry

Business requirements

• Reduce unnecessary scanner load and repeated failed scan attempts

• Improve operational clarity for security teams

• Detect and highlight deployments running images no longer present in the registry

• Prevent confusion around scan failures

• Reduce support cases related to repeated 404 scan errors