---
title: "Distinguish missing image attestations from incorrect ECS scope | Proofline Help"
description: "When no running image can be tied to a commit, use the repository named by Publish build provenance to identify which build should attest the image digest."
url: https://proofline.sh/help/inbox-deploy-provenance-missing/
---

[Help center](/help/)

# Distinguish missing image attestations from incorrect ECS scope

When no running image can be tied to a commit, use the repository named by Publish build provenance to identify which build should attest the image digest.

## Check the image build and the named ECS services

Open **Publish build provenance** and compare its requirements with the repository’s image build workflow. Check whether each named service is still deployed by that repository. If a service is still in use, keep it in scope and have the build publish qualifying provenance for its images.

If the task also identifies a service that is no longer deployed or should run tasks but runs none, **Edit ECS services** opens the account resource scope. An attestation for an unrelated image cannot establish which commit the service is running.

## Related guides

-   [Clear Inbox setup tasks](/help/inbox-setup-tasks/)
