A blocked pipeline is the control working. A policy check found something your organization decided should not ship. The check output names the check, its severity, and the changeset that triggered it. Read it before touching anything.

Read the failure

The pipeline log carries the checks run output. Each violation names the check that fired, what it requires, and the changeset or object responsible.

If operation reporting is configured, the same result is easier to read on the server. Open the Policy Checks view, find your run, and open it. The results are broken out under Findings on the details page. Start on the By Severity tab. It opens first when the run has violations, and each entry shows the severity, the check name, a description of what the check requires, the flagged changeset or database object, and the source file and line. Use the By Changeset tab to see everything flagged against one changeset at once. To confirm whether a check ran at all, or how it was configured, switch to By Check and expand the check's row. Every field on these screens is described in What are policy check results?.

Fix the change or raise the rule

Most failures are fixed in the changeset. Read what the check requires and update the change to meet it, for example adding a required comment or renaming an object to match conventions. Then rerun the checks locally with checks run before resubmitting. See Run a policy check. Checks execute in the CLI and your pipelines. The server is where the results are reviewed and where your organization manages the policies themselves.

Sometimes the rule is wrong for the case. Do not work around a check. Policies are defined, organized, and assigned by whoever owns governance in your organization, and changing a check's severity or scope is a deliberate decision made there, not in your changeset. See Understand policy governance. Whether a violation blocks the pipeline is configuration, not accident.

The full diagnostic workflow

The step-by-step diagnosis lives in Investigate a policy check failure. This page is the developer's side of it, covering what the failure means for your change and what to do next. When the fix is made, continue in Correct and resubmit the change.