---
title: "Investigate a deploy with no recorded decision | Proofline Help"
description: "Open Decisions for the environment and compare the deploy time with the gate setup and any recorded processing failures. A deploy may never have waited for Proofline."
url: https://proofline.sh/help/deploy-processing-failure/
---

[Help center](/help/)

# Investigate a deploy with no recorded decision

Open Decisions for the environment and compare the deploy time with the gate setup and any recorded processing failures. A deploy may never have waited for Proofline.

[![The Decisions page for Production shows that recent deploys did not wait for approval, with a link to delivery setup.](/help-images/deployment-decisions-light.png)](/help-images/deployment-decisions-light.png)

Production received deploys, but none waited for Proofline’s approval. Fictional demo workspace.

## Distinguish missing intake from a failed decision attempt

If recent deploys landed without waiting for Proofline, the page can show **No deployment review is starting**. On GitHub Actions, the deployment job must wait for Proofline’s protection rule. On Cloud Build, the bound trigger must require approval. An administrator can follow **Open delivery setup** to [check deployment protection](/help/deployment-protection/).

If **Deployment processing failures** lists an attempt, processing ended before Proofline recorded an authorization decision. Follow **Open associated review** when available. Expand **Failure record reference** for the gate reference and policy if you need to identify that attempt.

## Related guides

-   [Trace a deployment decision](/help/deployment-decisions/)
-   [Configure deployment protection](/help/deployment-protection/)
