If you are testing locally with (mock AWS) or the BigQuery Emulator , these tools do not fully support all SQL semantics or Artie’s DDL operations.
Have a different "local code with Artie" error? Share your log snippet in the comments below, and we will troubleshoot together.
, it is usually due to a connection mismatch or a browser protocol error. Because Artie acts as its own Wi-Fi hub, your device must be connected directly to Artie's network—not your home Wi-Fi—to access the coding page. Amazon.com Quick Fixes for Connectivity Check the URL Protocol : Ensure your browser is using local code with artie not working
For CDC testing, use a real cloud warehouse sandbox (Snowflake trial account costs $0). Or, use a local version of Redshift (Redshift Local) or DuckDB (if you modify Artie’s destination driver – not officially supported).
Go to your device's Wi-Fi settings and turn off "Auto-Join" or "Auto-Connect" for your home/school Wi-Fi network. If you are testing locally with (mock AWS)
go clean -modcache go mod tidy
✅ 1. with --verbose flag: artie transfer --config artie.yaml --verbose , it is usually due to a connection
The most common reason for is a discrepancy between your local environment and the environment Artie expects or creates.
Artie runs for 10 minutes, then crashes with too many open files .