Solution skill
LangSmith ingest failing from APAC: use the regional endpoint
Complete solution
Shows how to fix langSmith ingest failing from APAC: use the regional endpoint. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
If LangSmith ingest fails with connection errors from APAC even though it used to work, point the SDK at the regional endpoint: set LANGSMITH_ENDPOINT=https://apac.api.smith.langchain.com.
Steps
- If LangSmith ingest fails with connection errors from APAC even though it used to work, point the SDK at the regional endpoint: set LANGSMITH_ENDPOINT=https://apac.api.smith.langchain.com. The default US endpoint causes connection failures from APAC regions; switching to the regional endpoint fixed the ingest failures for the reporter.
When to use
You are seeing this: Issue langchain-ai/langsmith-sdk#1769 (closed, 20 comments): Failed to send compressed multipart ingest: connection errors when posting traces to the LangSmith API. Use this skill when you run into "LangSmith ingest failing from APAC: use the regional endpoint".
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 original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Sources
- https://apac.api.smith.langchain.com
- https://github.com/langchain-ai/langsmith-sdk/issues/1769
Evidence
In https://github.com/langchain-ai/langsmith-sdk/issues/1769, the reporter asked: Issue langchain-ai/langsmith-sdk#1769 (closed, 20 comments): Failed to send compressed multipart ingest: connection errors when posting traces to the LangSmith API. It used to work a few months ago. Tried with and without async mode, local (Ollama) and remote (Groq) LLMs, with and without a checkpointer. Every (a)invoke fails to ingest. The verified answer: If LangSmith ingest fails with connection errors from APAC even though it used to work, point the SDK at the regional endpoint: set LANGSMITH_ENDPOINT=https://apac.api.smith.langchain.com. The default US endpoint causes connection failures from APAC regions; switching to the regional endpoint fixed the ingest failures for the reporter. Source thread: https://github.com/langchain-ai/langsmith-sdk/issues/1769
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_mK_EFooTJ-B5XbGLXnJWXg" 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">LangSmith ingest failing from APAC: use the regional endpoint <span>— Vectle</span></a>