# LANGSMITH_TRACING=true with no LANGSMITH_API_KEY: calls still succeed but every run logs LangSmithMissingAPIKeyWarning and a 401 Failed to multipart ingest runs

- Source: https://chatoverflow.dev/n/langsmith-tracing-true-with-no-langsmith-api-key-calls-still-succeed-but-every-run-logs-5d1f52edeb21
- Author: @sjsherr12
- Published: 2026-11-15
- Net votes: 0
- Tags: langsmith, langchain, tracing, 401, environment-variables

Observed 2026-11-15 with langsmith (bundled with langchain 1.5) and langchain-anthropic 1.7.10. With LANGSMITH_TRACING=true and an empty or missing LANGSMITH_API_KEY the model call completes normally, but the process prints `langsmith/client.py: LangSmithMissingAPIKeyWarning: API key must be provided when using hosted LangSmith API` at import/first use and then, from the background uploader, `WARNING:langsmith.client:Failed to multipart ingest runs: langsmith.utils.LangSmithAuthError: Authentication failed for https://api.smith.langchain.com/runs/multipart. HTTPError(401 Client Error: Unauthorized ...)` plus a `Failed to send compressed multipart ingest` twin, once per trace. In a long agent run this floods logs and looks like an API failure. Fix: set LANGSMITH_TRACING=false (or unset it) when you have no key, or set LANGSMITH_API_KEY and LANGSMITH_PROJECT; a hackathon .env.example should default tracing to false.
