troubleshooting-datavault4dbt

# Troubleshooting datavault4dbt Diagnose datavault4dbt models by symptom. The package generates the SQL, so most issues trace back to the **staging metadata** (hashkeys/hashdiffs), the **YAML parameters**, or **incremental/HWM** behavior. ## First moves 1. `dbt compile --select <model>` and read the generated SQL in `target/` — it shows exactly what the macro produced. 2. Enable verbose package logs: set `datavault4dbt.show_debug_logs: true` in `vars:` and re-run, then read the dbt `.log` file. 3. Inspect the staging output (`dbt show --select <stage_model> --limit 20`) — most raw-vault problems originate one layer up, in staging. ## Symptom → cause → fix ### Satellite captures too many rows (a new record every load) - **Payload doesn't match the hashdiff inputs.** The satellite's `src_payload` must be exactly the columns fed into its hashdiff in staging. If they differ, change detection misfires. - **Trimming / case mismatch.** Untrimmed whitespace or case differences in descriptor values change the hashdiff each load. Check `hashdiff_use_trim` and `hashdiff_input_case_sensitive`. - **A volatile column is in the hashdiff** (e.g. a load timestamp or surrogate). Remove it from the hashdiff inputs. ### Satellite captures too few rows / misses changes - A changing attribute is **not** in the hashdiff inputs, so the change is invisible. Add it (and to `src_payload`). - For a single-attribute satellite, confirm you omitted `src_hashdiff` so change detectio...