Pipes Troubleshooting

1. Identify Error Type

Compilation Errors:

• TypeScript type mismatches
• Missing imports or dependencies
• ABI version conflicts (@subsquid/evm-abi 0.3.1 vs 1.x.x)

Runtime Errors:

• Portal API connection failures
• Database connection issues
• Event decoding errors
• Memory issues or OOM
• Cursor corruption

Data Quality Issues:

• Missing events
• Incorrect event parameters
• Duplicate records
• Wrong block ranges

2. Check Running Processes

If indexer is currently running:

# Check if process is running
ps aux | grep "npm run dev\|tsx src/index.ts\|node"

# Check output if running in background
# Use Bash tool with bash_id

3. Read Error Context

Always read the relevant files:

• src/index.ts - Main pipeline code
• package.json - Dependency versions
• .env - Connection strings
• Error stack traces from Bash

Common Error Patterns

Error Pattern 1: ABI Version Mismatch

Symptoms:

Type 'LogParams' is not assignable to type 'EvmLogParams'
Property 'topics' is missing in type 'LogParams'

Diagnosis: Wrong @subsquid/evm-abi version Root Cause: Using 1.x.x instead of 0.3.1

Fix:

// package.json
{
  "dependencies": {
    "@subsquid/evm-abi": "^0.3.1"  // NOT ^1.0.0
  }
}

Steps:

1. Read package.json
2. Edit to correct version
3. Run npm install or bun install
4. Verify types resolve

Error Pattern 2: Portal API Connection Failed

Symptoms:

Error: connect ECONNREFUSED
Error: Portal request failed with status 429
Error: Portal timeout after 30s

Diagnosis: Network or rate limit issue

Fix Options:

1. Rate Limiting (429): Add delay between requests or reduce block range
2. Connection Refused: Check internet connection, verify Portal URL
3. Timeout: Increase timeout or reduce batch size

Code Changes:

// Reduce block range to avoid rate limits