Understand Deployment Logs

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 and Admins, 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 — currently a Vercel deploy hook trigger, or Manual / No Automatic Deployment.
• 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 tracked to completion

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

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.

Retention

Deployment Logs are kept for a period that depends on your plan, then older entries are cleaned up. See Billing, trial, and plan limits.

Next steps

• Configure a deployment trigger to set up or change your method.
• Understand Publish Logs for the commit side of publishing.
• Troubleshoot publishing failures if a trigger keeps failing.