Traces Not Appearing in Dashboard
Check Connector Initialization
Make sure you’re callingconnector.init() before any LangChain operations:
Verify API Key
Check that your API key is correct:- Log in to Arcbeam
- Go to Settings → API Keys
- Verify the key exists and matches what you’re using
- Try generating a new key if needed
Check Network Connectivity
Verify your application can reach Arcbeam:Look for Error Messages
Check your application logs for errors from the connector:Authentication Errors
”Invalid API key” or “Unauthorized”
Causes:- API key is incorrect
- API key was deleted
- API key doesn’t have access to the project
- Copy the API key again from Arcbeam settings
- Check for extra spaces when pasting the key
- Verify the key starts with
sk- - Try creating a new API key
Wrong Base URL
Make sure you’re connecting to the correct Arcbeam instance:Some Operations Not Being Traced
Connector Initialized Too Late
The connector must be initialized before creating any LangChain components:Using Unsupported LangChain Features
Not all LangChain features are automatically traced. If you’re using custom callbacks or unusual patterns, traces might not be captured. Workaround: Stick to standard LangChain patterns (chains, agents, retrievers) which are fully supported.Performance Issues
High Latency
Traces are sent asynchronously and shouldn’t add latency. If you’re experiencing slowdowns:- Check network latency to Arcbeam
- Verify Arcbeam platform is responsive (check status page)
- Try reducing trace volume temporarily to isolate the issue
Memory Usage
The connector batches traces before sending. If you’re seeing high memory usage:- Check for trace backlog - if Arcbeam is unreachable, traces queue up
- Reduce concurrent requests if running many parallel operations
- Verify network connectivity so traces are sent promptly
Environment Variable Issues
Variables Not Loading
If environment variables aren’t being read:Using .env Files
If using a.env file:
- Make sure the file exists in your project root
- Add
.envto.gitignore(don’t commit it!) - Load it before accessing variables
Project ID Issues
”Project not found”
If you’re specifying a project ID and getting errors:- Copy the project ID from the Arcbeam dashboard (Projects page)
- Check for typos in the UUID
- Try omitting project_id to use the default project
- Verify the project exists and you have access to it
LangChain Version Issues
Incompatible LangChain Version
The Arcbeam connector requires specific LangChain versions. Check your versions:Import Errors
”ModuleNotFoundError: No module named ‘arcbeam_connector’”
The connector isn’t installed:“ModuleNotFoundError: No module named ‘langchain’”
LangChain isn’t installed:Self-Hosted Arcbeam Issues
Cannot Connect to Local Instance
If running Arcbeam locally:- Wrong port - Default is 5173, verify your instance
- Using https instead of http for localhost
- Firewall blocking the connection
- Arcbeam not running - check
docker psor your deployment
SSL Certificate Errors
For self-hosted instances with custom SSL:Still Having Issues?
If you’re still experiencing problems:Check the logs
Look for error messages in your application logs. The connector will log errors if trace sending fails.
Check Arcbeam status
Verify the Arcbeam platform is operational (check status page or contact support).
Contact support
Email support@arcbeam.ai with:
- Your error messages
- Code snippet showing how you’re initializing the connector
- LangChain and connector versions
- Whether you’re using cloud or self-hosted Arcbeam
Debugging Checklist
Before contacting support, verify:-
connector.init()is called before LangChain operations -
ARCBEAM_API_KEYenvironment variable is set - API key is correct (starts with
sk-) - Can reach Arcbeam platform (
curl http://platform.arcbeam.ai) - Using compatible LangChain versions
- No error messages in application logs
- Firewall/network allows outbound HTTP to Arcbeam
Common Error Messages
| Error | Cause | Solution |
|---|---|---|
Invalid API key | Wrong or deleted API key | Copy key again from Arcbeam settings |
Project not found | Invalid project_id | Verify UUID from dashboard or omit to use default |
Connection refused | Cannot reach Arcbeam | Check network, firewall, and base_url |
Module not found | Package not installed | Run pip install arcbeam-connector |
No traces appearing | Connector not initialized | Call connector.init() before LangChain |
