Fix deployment trigger failures

When Acrosite committed your content but the deployment trigger did not fire, here is how to diagnose and fix it — without exposing your hook URL.

TroubleshootingFor DevelopersUpdated June 8, 2026

Sometimes Acrosite commits your content successfully but the deployment trigger does not fire. The good news: your content is already in the repository, so you only need the redeploy to go through. This guide covers it.

Who this is for

Developers who manage Deployment Setup.

Confirm the stage

Open Deployment Logs and find the recent trigger request and its status.
If the commit succeeded but the trigger failed, the issue is at the deployment stage, not GitHub.

Common causes

The hook URL was revoked or regenerated in your provider. Re-copy it and save it again in Deployment Setup.
The endpoint is temporarily unavailable. Check your provider's status, then retry.
The method is misconfigured. Confirm the correct method in Configure a deployment trigger, and use Test Deployment Trigger to send a safe test. See Test your deployment trigger.

A failed trigger does not undo the commit

Note

A failed deployment trigger does not undo the commit. Your content is already committed; you only need the redeploy to fire. You can retry just the deployment without recommitting. See Retry a failed publish or deployment.

Triggered, not completed

Remember that a successful trigger only means your provider accepted the request. Acrosite does not track the build to completion, so confirm the finished build in your provider's dashboard.

Hook URLs stay masked

Your hook URL is stored server-side and shown masked. When you replace it, the full URL is not shown again after saving. Never share a hook URL in a support request.

Next steps

Frequently asked questions

My content committed but did not deploy. Did I lose it?

No. Your content is already in your GitHub repository. A failed deployment trigger only means the redeploy did not fire — retry just the deployment, no recommit needed.

How do I test my deployment trigger safely?

Use Test Deployment Trigger in Deployment Setup. It sends a test request to your hook and shows whether your provider accepted it, without publishing real content.

Does a successful trigger mean my site is updated?

Not necessarily. A successful trigger means your provider accepted the request. Acrosite does not track the build to completion, so confirm the finished build in your provider's dashboard.

PreviousFix GitHub connection issues NextContent is not showing on my site