GitHub Actions "deployment protection rule timed out"

By Daniel Zoghalchali·Latchkey

Custom deployment protection rules call an external app that must respond within the allowed window. If the integration never posts a result, the gate times out and the deployment is rejected. A flaky callback can be transient.

What this error means

A deployment that depends on a third-party protection-rule app fails after the wait window with a timeout, never receiving approve or reject.

Error: Deployment protection rule timed out waiting for a response from the integration.

Common causes

External app never responded

The protection-rule integration did not post an approval/rejection within the window, so GitHub timed out the gate.

Transient callback failure

A temporary outage or network blip in the integration delayed the callback past the deadline.

How to fix it

Recover the protection-rule callback

1. Check the external protection-rule app logs for the deployment event delivery.
2. Re-run the deployment to re-trigger the gate once the integration is healthy.
3. If the app is misconfigured, fix its webhook handling so it posts a result within the window.

How to prevent it

• Make protection-rule integrations respond promptly and idempotently.
• On Latchkey managed runners, transient gate-callback timeouts on re-run are retried automatically so a one-off integration blip does not strand the deploy.

Frequently asked questions

Related guides

References

• GitHub Actions documentation
• Workflow syntax for GitHub Actions