builds

The deployment list

Loads on open; the refresh icon in the panel header reloads it. Each deployment shows a status dot and label, the branch it came from, how long the build took, the commit message and when it finished.

Error details

Failed deployments get a Show error details toggle, which fetches the build log for that deployment and pulls out two things:

• Prerender errors - one row per page that failed to render, with its HTTP status, the path, and the page that linked to it where the log records one. This is the fastest way to find the document behind a broken build.
• Build log excerpts - the error lines from the log, for failures that are not page specific, such as a bad import or an environment variable that is missing at build time.

Details are fetched once per deployment and kept while you stay on the page, so reopening a row is instant.

How it relates to the other tabs

url_audit and sitemap both read the most recent deployment. If either produces surprising output, check here first: a failed or partial build explains a sudden pile of missing URLs better than anything in Prismic does.

Prerender errors listed here and missing URLs in url_audit are frequently the same pages seen from two directions - one says the build could not render it, the other says it never got built.

Requirements

Vercel project ID and token, plus the team ID if the project belongs to a Vercel team. The token needs read access to deployments.