Find the Friday build failure on Friday

What does the deploy check cover?

Which sites have a failed build, when the last successful deploy happened, and whether what is published matches the branch anybody thinks is live. That last one catches the confusing case: a locked deploy, or a publish somebody rolled back and nobody announced.

Read the Available tools list on the Netlify entry under `strawberry://settings/integrations` first, because it names each tool and marks the read-only ones. Then set the mode for each in the Permissions block. Reads at Always allow is comfortable here. Publishing is not.

Why is publishing a deploy the sharp edge?

Because it takes effect on the live site in seconds with no staging step in between.

Restoring a previous deploy is equally instant, which cuts both ways: recovery is fast, and so is the mistake.

So keep publish and rollback actions at Ask every time and read the approval rather than clicking it. Consequential steps stop at an approval card anyway. If nobody on your team should be publishing from a chat window, switching the action off says so permanently.

• Site and deploy status reads: the morning check, low risk.
• Publish and restore actions: instant on the live site, so keep an approval in front of them.
• Environment variable reads expose secrets, exactly as they do anywhere else.
• A token scoped to the team or sites you actually want visible.

Join the failed build to what caused it

A failed Netlify build is almost always explicable from its log: a missing environment variable, a dependency that changed, a function bundle over the size limit. Whether a companion reads that log depends on whether such an action is in the tool list, so check before you plan a triage workflow.

What it always does is find the cause in the browser: the commit that broke it, the pull request that introduced the dependency, the person who changed the environment variable an hour earlier. Assembling that is what makes a postmortem worth reading, and paired with Vercel or GitHub accounts it covers a whole deploy pipeline.

Frequently asked questions