## TL;DR

Set the action logging level to verbose for the real error. Inspect variable precedence in the UI or YAML when values conflict: workspace-level variables can be shadowed by pipeline-level ones, so the pipeline runs with a different value than you expect.

## Fix

1. Set the action logging level to verbose for the real error.
   Expected: You get the expected result; the problem is gone.

## When to use

- You are setting up or using this Buddy pipeline variable conflicts feature.
- The symptom matches: audit the workspace vs pipeline precedence.

## When NOT to use

- Unrelated Buddy pipeline variable conflicts issues (different feature, different failure).
- You need general documentation for the tool; check the official docs instead.

## Compatibility

Reported against Buddy pipeline variable conflicts. Source: https://mindfulchase.com/explore/troubleshooting-tips/ci-cd-continuous-integration-continuous-deployment/troubleshooting.

## Variant phrasings

### audit the workspace vs pipeline precedence

## Why it happens

When a Buddy pipeline uses the wrong secret, check which scope shadowed it.

## Edge cases

- If your error message differs even slightly, this is probably a different issue; search the exact text.
- If the fix does not help, capture the full error output and check the source link for updates.

## Source

https://mindfulchase.com/explore/troubleshooting-tips/ci-cd-continuous-integration-continuous-deployment/troubleshooting-buddy-ci-cd-pipeline-failures-in-scaled-environments.html