> ## Documentation Index
> Fetch the complete documentation index at: https://docs.exmergo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Understand a refusal or incomplete result

> Find the next step when Dex needs confirmation, lacks a dependency, refuses a query, or cannot verify a build. Resolve the cause without bypassing the guards.

Start with the JSON envelope's `status`, `reason`, `errors`, and `warnings`.
A refusal explains a boundary; a successful result may still contain findings
or checks that did not run.

## Choose the symptom

> [accordion] The command returns needs\_confirmation
>
> Read what it is asking you to approve. A cost estimate, configuration diff, and
> file changed since planning require different decisions.
>
> For spend, follow [cost controls](https://docs.exmergo.com/dex/guardrails/cost-controls.md). For a config
> change, review the diff in [`dex config`](https://docs.exmergo.com/dex/cli/config). If a planned file has
> changed, plan again against the current file before applying.
>
> Do not treat `--confirm` as a universal retry flag.

> [accordion] uv or a connector dependency is missing
>
> Check `uv --version` in the terminal your agent uses. Follow
> [Installation](https://docs.exmergo.com/dex/installation.md) if it is missing. A `reason: prerequisite`
> response names the extra the command needs; install that extra or use the skill
> wrapper that selects it. Do not replace the command with a raw warehouse client.

> [accordion] Dex cannot find the connection or project
>
> Run from your project directory, inspect `dex config get`, and run
> `dex config validate`. Then use `dex connect test` to check the selected target.
> See [Connect your data](https://docs.exmergo.com/dex/connect.md) for connector discovery and scope.
>
> For dbt, check that Dex can discover one project or that `dbt_project_dir`
> selects the intended one. `DBT_PROFILES_DIR` locates dbt profiles; it does not by
> itself select Dex's connector.

> [accordion] A query is blocked by a PII flag
>
> Read the [PII policy](https://docs.exmergo.com/dex/guardrails/pii-policy.md). Only a human clears a flag.
> If an aggregate answers the question, ask for the aggregate instead of returning
> individual values. Do not alter flags to make a query pass.

> [accordion] The demo refuses to create its files
>
> Use a fresh directory outside an existing Dex project. The demo is create-only
> and will not replace an existing warehouse file. A configuration above the
> directory can also keep it from creating the demo configuration. See the
> [quickstart](https://docs.exmergo.com/dex/quickstart.md).

> [accordion] The build succeeds but verification reports a problem
>
> Read `data.verification`, including findings and suppressed checks. A successful
> dbt run does not prove the population, joins, or grain are right. Investigate
> row loss, fan-out, and NULL columns, fix the plan, then rebuild with `--verify`.
> A `column_missing`, `column_undeclared`, or `column_type_mismatch` finding means
> the built relation and `schema.yml` disagree: fix whichever is out of date.
> See [Transform a dbt project](https://docs.exmergo.com/dex/guides/transform.md).

> [accordion] A map or drift check looks incomplete
>
> Read the elision counts, skipped objects, suppressed checks, and any optional
> measurement offer. Narrow the question or request the missing evidence.
> A check that did not run is not a clean result. See
> [Explore](https://docs.exmergo.com/dex/guides/explore.md) or [Maintain](https://docs.exmergo.com/dex/guides/maintain.md).

For the exact response fields, use the
[command contract](https://docs.exmergo.com/dex/reference/command-contract.md#the-envelope).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.