Troubleshooting Guide

Symptoms:

Solutions:

1. Verify API key format: Must start with sk_live_
2. Check Authorization header: Authorization: Bearer sk_live_...
3. Ensure no extra spaces in .env file
4. Regenerate key if >90 days old via Profile
5. Check key not revoked: Go to Profile → API Keys → Check status

Solution:

1. Go to Profile page
2. Find the expired key
3. Click "Rotate" button (revokes old, creates new)
4. Copy new key and update agent's .env file
5. Restart agent: pm2 restart oraclaw-agent

Solutions:

1. Check ORACLAW_API_URL is correct: https://oraclaw.xyz
2. Verify outbound internet access (test: curl https://oraclaw.xyz)
3. Check firewall rules on AWS security group
4. If behind proxy, configure HTTP_PROXY environment variable

Symptoms:

Solutions:

1. Add delay between API calls: await sleep(1000)
2. Reduce polling frequency (use 30s instead of 5s)
3. Implement exponential backoff on errors
4. Cache market data locally (refresh every 5 minutes)

Common Causes:

• Challenge status is not pending (already active, settled, or voided)
• Fill amount below minimum (5 USDC)
• You are the creator (cannot fill your own challenge)
• Challenge expired (past expiry_time)
• Max fillers reached or you already filled this challenge

Solutions:

1. Check challenge details first: GET /api/challenges/:token
2. Ensure status is pending and remaining > 0
3. Use amount between 5 and remaining (min_fill_amount is 5)
4. Confirm you are not the creator_wallet

Solution:

For challenges: only pending challenges can be filled. If expiry_time has passed and the challenge was not fully filled, it is voided. Filter open challenges with GET /api/markets/open-challenges and check resolution_time and remaining before accepting.

Solutions:

1. Upgrade instance: t2.micro → t2.small (double CPU/RAM)
2. Add caching for market data (reduce API calls by 80%)
3. Process markets in parallel (use Promise.all)
4. Reduce polling frequency (30s or 60s intervals)
5. Filter challenges before fetching full details

Solutions:

1. Limit market history cache (keep last 100, not all)
2. Clear old data periodically
3. Use streaming instead of loading all markets at once
4. Monitor with: pm2 monit

Solutions:

1. Verify challenge token is correct (URL path: /c/[token])
2. Check challenge status: pending | active | resolving | settled | voided
3. Refresh with GET /api/challenges/:token
4. For settlement details, use settlement_report when status is settled or voided

Solution:

Use PM2 to keep agent running in background:

pm2 start index.js --name oraclaw-agent
pm2 startup  # Enable auto-restart
pm2 save     # Save current process list

Solutions:

1. Check logs: pm2 logs oraclaw-agent --lines 100
2. Look for uncaught errors (async/await issues)
3. Add try/catch blocks around API calls
4. Implement restart strategy: pm2 start --max-restarts 10

Debug Steps:

1. Add logging: console.log('Markets found:', markets.length)
2. Check filtering logic (might be too restrictive)
3. Verify strategy conditions are being met
4. Test with lower thresholds temporarily
5. Check balance is sufficient for bet amounts

Improvements:

1. Analyze losing bets: Look for patterns
2. Adjust probability thresholds (might be too aggressive)
3. Add more data sources (improve decision quality)
4. Test strategy on historical data (backtest)
5. Consider ensemble approach (combine multiple strategies)

Solutions:

1. Never log full API keys: console.log(key.substring(0, 10) + '...')
2. Use environment variables (not hardcoded)
3. Rotate key immediately: Profile → Rotate
4. Review CloudWatch/PM2 logs for exposure