Skip to content

Troubleshooting

General issues

skippr.yaml not found

Run skippr init <project> in the working directory first.

Need to fully reset a project

If you want to clear the current project's accumulated run state and start fresh, run:

bash
skippr init <project> --reset

This will prompt you to type yes, clear the project's run state, and recreate a clean working environment so you can reconnect and rerun from scratch.

dbt: command not found

Activate the Python virtual environment before running skippr:

bash
source .venv/bin/activate
dbt --version

If dbt is not installed:

bash
pip install dbt-core dbt-snowflake   # or dbt-bigquery

LLM errors (401 / timeouts)

  • The LLM key is provided by the server after authentication. If you see a 401 from the LLM, check that your Skippr account is active and has credits.
  • If you set LLM_API_KEY to use your own key, confirm it is valid and has not expired.
  • If requests timeout, set LLM_HTTP_TIMEOUT_SECS=120 in the environment.
  • If output is truncated, set LLM_MAX_TOKENS=8192.

API key errors (401 / "API key exchange failed")

  • Confirm SKIPPR_API_KEY is set to a valid sk_live_… key.
  • The key may have been revoked — check with skippr user list-api-keys.
  • If the key was recently created, wait a few seconds for propagation.
  • Check the auth service URL: SKIPPR_AUTH_URL defaults to https://auth.skippr.io.

"No credits remaining"

Your account balance is zero. Add funds to continue:

bash
skippr user buy-credits --amount 25

Sync stalls with no output

The extract-and-load step produced no output within the idle timeout. Common causes:

CauseFix
Warehouse connection hangingCheck credentials and network access
Source credentials missingVerify environment variables for your source

dbt deps needed

After the first run, skippr generates a packages.yml in the dbt project. If dbt reports missing packages, run:

bash
source .venv/bin/activate
dbt deps

Provider-specific issues

See the connect guide for your provider: