Troubleshooting¶
Symptom first, for the example pipelines. An error from allez itself is on the other troubleshooting page.
Pipelines¶
| You see | Cause | Do |
|---|---|---|
A merge to main queued no run |
The change touched nothing under fabric/ or .allez/hooks/ (path filter), or the pipeline is not registered. |
Nothing to deploy for the first; register the YAML for the second (register the pipelines). |
The run is named 20261014.2, not a version |
GitVersion did not run or could not see the tags: a shallow checkout, or GitVersion.yml missing from the repo root. |
Every checkout: self needs fetchDepth: 0 and fetchTags: true; copy GitVersion.yml from allez-example to your root. |
tag the prod commit failed with TF401027 or 403 on git push |
The build service identity cannot write to the repo. | Grant it Contribute and Create tag under the repo's security (setup). |
Could not list remote branches (git ls-remote --heads) |
The agent's checkout did not keep its credentials, or the local repo has no remote. | checkout: self with persistCredentials: true (deploy.yml's Dev job has it); locally, check the remote. |
teardown --orphans says Nothing to tear down while orphans exist |
The service principal has no role on them (scopes), the branch still exists on the remote, or branch-workspace.git.repository does not match the workspace names. |
Give it a role (roles); delete the source branch on merge; check branch-workspace.git.repository. |
| A deploy failed because the capacity was paused, or Fabric answered 429 | The infrastructure could not take the deploy; nothing in the repo is wrong. | Resume the capacity or wait, then re-run the failed stage from the run page. |
| Approval prompt shows only a commit hash | You are looking at the environment approval, not the plan. | Open the log of the plan job (PlanProd) in the Test stage, or the plan-prod artifact; that is what the approval is for. |