Configuration Issues
Error: Item missing required field
Error: Item missing required field
Error Message:Cause: Your item configuration is missing a required parameter.Solution:Ensure every item has all required fields:Required fields for all endpoints:
config.yaml
market_hash_nameappidapiidpolling-interval-in-seconds
item_nameidis required foritemordershistogramanditemordersactivity
Error: Invalid apiid
Error: Invalid apiid
Error Message:Cause: You’ve specified an API endpoint that doesn’t exist.Solution:Use one of the four supported endpoint names:
priceoverview- Current prices and 24h volumeitemordershistogram- Order book dataitemordersactivity- Recent trading activitypricehistory- Historical hourly data
config.yaml
Error: Missing item_nameid
Error: Missing item_nameid
Error Message:Cause: You’re using
itemordershistogram or itemordersactivity without providing the item_nameid.Solution:Find the item_nameid using browser DevTools:Error: Infeasible configuration
Error: Infeasible configuration
Error Message:Cause: Your polling intervals would exceed the rate limit.Calculation:Solutions:
- Increase polling intervals:
-
Reduce tracked items:
Comment out or remove some items from
TRACKING_ITEMS. - Increase rate limit (if safe):
Error: Unable to load config.yaml
Error: Unable to load config.yaml
Error Message:Cause: The
config.yaml file doesn’t exist or is in the wrong location.Solution:- Ensure
config.yamlis in the same directory ascerebro.py - Check file name spelling (case-sensitive on Linux/Mac)
- If running from a subdirectory, use the full path:
Authentication Issues
Error: 401 Unauthorized (pricehistory endpoint)
Error: 401 Unauthorized (pricehistory endpoint)
Cookies expired
Cookies expired
Rate Limiting Issues
Error: 429 Too Many Requests
Error: 429 Too Many Requests
Error Message:Cause: You’ve exceeded Steam’s rate limits.Solution:
- Check your rate limit settings:
config.yaml
- Increase polling intervals: Reduce request frequency:
- Wait before retrying: If you’re rate-limited, wait 1-2 minutes before restarting.
Requests are queuing/slow
Requests are queuing/slow
Symptoms:If capacity is >90%, requests will queue during peak times.Solution:
- Long delays between requests
- Items not updating at expected intervals
- Increase polling intervals for low-priority items:
- Reduce tracked items: Remove or comment out items you don’t actively monitor.
- Increase rate limit (cautiously):
Database Issues
Error: Database is locked
Error: Database is locked
Error Message:Cause: Multiple processes are trying to write to the database simultaneously.Solution:
- Check for multiple instances:
- Close SQLite connections: If you have SQLite CLI or database browsers open, close them.
- Wait and retry: SQLite locks are usually temporary. Wait a few seconds and try again.
No data in database
No data in database
Symptoms:Solution:
market_data.dbexists but tables are empty- Queries return no results
- Check if Hridaya is running:
- Verify configuration:
- Check tables exist:
- Ensure Hridaya is running:
python cerebro.py - Wait for the first polling interval to complete
- Check for error messages in console output
Query returns 'no such column'
Query returns 'no such column'
Error Message:Cause: Typo in column name.Solution:Check exact column names:Common mistakes:
market_name→market_hash_name✓item_id→item_nameid✓timevstimestamp(depends on table)
Network Issues
Error: Connection timeout
Error: Connection timeout
Error Message:Cause: Network connectivity issues or Steam is down.Solution:
- Check internet connection:
- Check Steam status: Visit steamstat.us or try accessing Steam Market in your browser.
- Check firewall: Ensure your firewall allows outbound HTTPS connections.
-
Increase timeout (if on slow network):
Edit
cerebro.py:steamAPIclient.py:36:
Error: SSL certificate verification failed
Error: SSL certificate verification failed
Error Message:Cause: SSL certificate issues (often corporate proxies or outdated certificates).Solution:
- Update certificates:
- If behind corporate proxy: You may need to configure proxy settings or install corporate root certificates.
Data Quality Issues
Prices seem incorrect
Prices seem incorrect
Symptoms:Solution:Ensure your
- Prices are much higher/lower than expected
- Decimal points in wrong place
- Check currency setting:
- Verify in database:
currency setting matches your expectations:1= USD ($)2= GBP (£)3= EUR (€)5= RUB (₽)7= BRL (R$)
Missing data points
Missing data points
Symptoms:
- Gaps in time series data
- Expected data points are missing
- Hridaya was stopped: Check if there were periods when the system wasn’t running.
- Rate limiting: If at capacity, some requests may be delayed or skipped.
- Network issues: Temporary connectivity problems.
- Steam API errors: Steam occasionally returns errors for specific items.
- Keep Hridaya running continuously (use systemd/supervisor in production)
- Monitor logs for errors
- Ensure adequate rate limit capacity
Duplicate timestamps
Duplicate timestamps
Symptoms:
- Multiple rows with identical timestamps
- Unexpected duplicate data
DISTINCT or aggregation:Performance Issues
High CPU usage
High CPU usage
Cause: Multiple concurrent async tasks and database writes.Solution:
- Reduce polling frequency:
- Reduce tracked items: Comment out low-priority items.
- Optimize database:
Database file growing rapidly
Database file growing rapidly
Symptoms:Solution:
market_data.dbis very large (>1GB)- Disk space running out
- Archive old data:
- Reduce polling frequency for historical data:
Slow queries
Slow queries
Symptoms:
- Queries take >1 second
- Database feels sluggish
- Always filter by item name:
- Use LIMIT for large results:
- Optimize database:
Getting Help
If you’re still experiencing issues:Next Steps
Tracking Items
Learn how to configure item tracking
Querying Data
SQL query examples and tips