Solution skill
Diagnose: tracing enabled but no traces appear in LangSmith
Complete solution
Shows how to fix diagnose: tracing enabled but no traces appear in LangSmith. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Run the smallest possible agent invoke and watch the project. Is LANGSMITH_TRACING=true actually set in the process that runs the agent?
Steps
- Is LANGSMITH_TRACING=true actually set in the process that runs the agent? Check from inside the process, not the shell you think launched it. Containers, schedulers, and notebooks routinely drop env vars.
- Is LANGSMITH_PROJECT pointing where you are looking? The default project is literally named
default. Check you are not staring at a custom project while traces land indefault. - Is LANGSMITHAPIKEY valid (see the 401 diagnostic)?
- The usual order: variable set after the process started, variable set in the wrong shell, or looking at the wrong project. No code changes are needed to trace;
create_agenttraces automatically once the env vars are right. - Export the variables before running:
- - LANGSMITH_TRACING=true
- LANGSMITHAPIKEY holding your key
- LANGSMITH_PROJECT set to the project you want (optional)
- Run the smallest possible agent invoke and watch the project. A trace appearing within a minute confirms the setup. If it appears in
defaultinstead of your project, the project variable is the problem.
When to use
You are seeing this: No traces in the LangSmith project despite expecting them. Use this skill when you run into "Diagnose: tracing enabled but no traces appear in LangSmith".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The usual order: variable set after the process started, variable set in the wrong shell, or looking at the wrong project.
Evidence
Diagnostic procedure grounded in the official trace-with-LangChain and observability docs, verified 2026-09-26. Tracing: docsgchain.com/langsmith/trace-with-langchain ; observability: docsgchain.com/oss/python/langchain/observability
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_CmhbPk9-0UxkaTUXOLcW7Q" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Diagnose: tracing enabled but no traces appear in LangSmith <span>— Vectle</span></a>