Pipeline Failure Troubleshooting

Common Failures

NuGet Restore Failures (HISD)

Symptom: Unable to find version of package or 401 Unauthorized Fix:

1. Check Azure Artifacts feed is accessible
2. Verify NuGet.config has correct feed URL
3. Check service connection permissions in Azure DevOps

.NET Build Failures (mobile-api, mgmt, cli)

Symptom: error MSB... or dotnet restore failed Fix:

1. Check if the .NET SDK version matches the pipeline’s UseDotNet task
2. Verify all project references resolve
3. Run locally: dotnet build --verbosity detailed

Flutter Build Failures (mobile-ui)

Symptom: flutter pub get failed or Dart analysis errors Fix:

1. Check Flutter SDK version in pipeline matches local
2. Run flutter doctor locally
3. Check for breaking package updates in pubspec.lock

Database Project Build Failures (HISD/HisdDb)

Symptom: SQL71501: Procedure has an unresolved reference Fix:

1. Check for missing schema objects in the .sqlproj
2. Verify dacpac references are current
3. Build locally in Visual Studio

Deployment Failures

Symptom: App Service deployment failed or slot swap failed Fix:

1. Check App Service is running: az webapp show --name <app> --query state
2. Check deployment logs: Azure Portal > App Service > Deployment Center
3. Verify Key Vault access policies

Retrying a Pipeline

# List recent failed runs
az pipelines runs list --status failed --top 5

# Re-run a specific pipeline
az pipelines run --name "<pipeline-name>" --branch <branch>