On this page
Publishing

Understand Deployment Logs

Deployment Logs record each deployment trigger Acrosite sends after a commit, including the response status. A trigger does not mean the build finished; build status is shown with each publish.

ReferenceFor Owners, Admins and DevelopersUpdated November 12, 2026

Deployment Logs record each deployment trigger Acrosite sends after committing content. They are how you confirm that your site was asked to rebuild — and see the response your provider gave. This page explains what they show.

Who this is for

Workspace Owners, Admins and Developers, who can view the workspace Deployment Logs. The logs are read-only.

What Deployment Logs record

After Acrosite commits content to your repository, it sends your configured deployment trigger. Each trigger creates a Deployment Log entry that includes:

  • The deployment method used — a Vercel, Netlify or Cloudflare Pages deploy hook, or no trigger (Git-connected or Manual).
  • The kind of trigger — a publish, a test, or a retry.
  • The response status returned when Acrosite called your trigger.
  • Whether the trigger succeeded or failed, and a short error summary if it failed.
  • The time it ran.

Triggered, not finished

This is the most important thing to understand about Deployment Logs:

Important
Deployment Logs record the trigger and the response to it. A successful trigger means your provider accepted the request; it does not mean the build finished or that the new content is live. Owners and Admins see the build status your host reports to GitHub with each publish, in Publish Logs and Publishing — see Build status.

Where to find Deployment Logs

Open your workspace and go to Deployment Logs (under the workspace logs area). You can filter and page through entries and open one for details. Entries link back to the related publish and content context where available.

Note
Like Publish Logs, Deployment Logs are sanitised. They never show your deploy hook URL, provider secrets, or raw provider payloads.

Retention

Deployment Logs show the period your plan includes. Older entries are hidden from the page but kept while the workspace exists, so that publishing problems can be investigated, and they are deleted when the workspace is removed. See Billing, trial, and plan limits and the Privacy Policy.

Next steps