troubleshootlisted

# troubleshoot > **Status**: v0.10.0 — references written; diagnostic playbook operational. Now covers the **dlt-era ingest failure modes** — the silent data gap (a mis-set incremental cursor that skips rows without crashing), a partial load (`_dlt_loads` status non-zero), a source-vs-destination reconciliation mismatch, and a systemd timer that didn't fire — alongside the original Airbyte/dbt/BQ/MCP modes. ## What this skill does Walks through the most common failure modes of the MDS in order of likelihood, gathering evidence from each layer. The agent reasons over the evidence to identify the cause and proposes (but does not execute) a fix. The user confirms before any change is applied. ## Preflight ```bash if [ ! -f .agentic-data-engineer.json ]; then echo "[abort] not a managed MDS deployment" exit 1 fi ``` ## Standard diagnostic flow Run checks in this order — earlier failures often explain later ones: **1. Tailscale reachability** ```bash ssh -i ~/.ssh/deploy_<client> root@<vps-tailscale-hostname> "tailscale status" ``` If unreachable: the VPS is offline, Tailscale on the VPS is down, or Tailscale on the laptop is down. **2. VPS processes and timers** ```bash ssh ... "uptime && free -h && df -h /" # load, RAM, disk ssh ... "systemctl list-timers 'dlt-*' 'dbt-*' --all --no-pager" # default: dlt + dbt timers (NEXT/LAST) ssh ... "journalctl -u dlt-<source>.service -u dbt-run.service --since '2 days ago' --no-pager | tail -40" ssh .