▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ Bicep Cost Estimator ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ Estimate Azure costs directly from Bicep and ARM templates. ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ title : Troubleshooting ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ page : https://bicepcostestimator.net/guides/troubleshooting ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ repo : https://github.com/polatengin/washington ▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄ This page covers the most common setup and estimation issues in Washington.  bce : command not found ──────────────────────── Install the published CLI or point directly at a local build: ┌─ bash example ───────────────────────────────────────────────────────────────────┐ │curl -sL https://bicepcostestimator.net/install.sh | bash │ │ │ │# or from the repo root │ │./src/cli/bin/Release/net10.0/bce estimate --file ./tests/fixtures/simple-vm.bicep│ └──────────────────────────────────────────────────────────────────────────────────┘ When you estimate a  .bicep  file, Washington will use a configured  bicep  binary if one is available on  PATH  or through  WASHINGTON_BICEP_CLI_PATH . Otherwise it downloads a pinned Bicep CLI release automatically. To restore the repo's .NET dependencies from a fresh clone, run: ┌─ bash example ─────────────────────────────────────┐ │make setup-cli │ └────────────────────────────────────────────────────┘ File not found or empty output ────────────────────────────────  bce estimate  requires  --file  and will emit an error if the path does not exist. For table output, a template with no supported resources can legitimately produce a nearly empty report. Check: • the file path you passed to  --file  • whether the template contains resources after compilation • whether those resource types are covered in Supported Resources https://bicepcostestimator.net/guides/supported-resources  No pricing mapper ... skipped  ─────────────────────────────── This warning means the resource extractor found a resource, but Washington does not yet have a mapper for that Azure resource type. What to do: • confirm whether the resource type appears in Supported Resources https://bicepcostestimator.net/guides/supported-resources • split the template into smaller test files to see which resource is missing coverage • treat the report total as partial until a mapper exists for that resource Unexpected  eastus  pricing ─────────────────────────── If Washington cannot resolve a location expression, it falls back to  eastus . Common causes: • the location comes from an ARM expression that is not fully resolved • the value is indirect through parameters or variables that do not collapse to a simple string at extraction time If regional accuracy matters, prefer explicit locations or verify the compiled ARM template first. Stale pricing or suspicious totals ──────────────────────────────────── Washington caches Azure Retail Prices API responses for 24 hours in: ┌─ text example ─────────────────────────────────────┐ │~/.bicep-cost-estimator/cache │ └────────────────────────────────────────────────────┘ Clear the cache and rerun: ┌─ bash example ─────────────────────────────────────┐ │bce cache clear │ │bce cache info │ └────────────────────────────────────────────────────┘  .bicepparam  file does not change the estimate ─────────────────────────────────────────────── Washington applies values from  .bicepparam  files and  --param  overrides during resource extraction. If the estimate still does not change, check: • whether the parameter actually influences a priced property such as SKU, instance count, or location • whether the parameter flows through a template expression the extractor can resolve • whether you passed the correct  .bicepparam  file for the template you are estimating VS Code extension does not show costs ─────────────────────────────────────── Check the following in order: 1. Open a  .bicep  file, since the extension activates on the Bicep language. 2. Set  washington.cliPath  if you want to force a known  bce  binary. 3. If  washington.cliPath  is empty, the extension will try the bundled binary, then a workspace  src/cli/washington.csproj , then  bce  on your  PATH . 4. If you expect automatic refresh, confirm  washington.estimateOnSave  is enabled. 5. Run  Washington: Estimate File Cost  manually from the command palette to verify the LSP path is working. Workspace estimate looks larger than expected ─────────────────────────────────────────────── The extension's workspace estimate walks every  .bicep  file recursively under the workspace root and aggregates all line items into one report. If your repo contains sample files, experiments, or duplicated environments, they will all be included. GitHub Action feels slow ────────────────────────── The action currently builds the CLI from source inside the workflow before running the estimate. That keeps the action self-contained, but it also adds startup cost compared with downloading a prebuilt binary. Related Reading ────────────────── • CLI Commands https://bicepcostestimator.net/cli/commands • VS Code Extension https://bicepcostestimator.net/vscode-extension • How Estimates Work https://bicepcostestimator.net/guides/how-estimates-work