---
title: "Common CLI Errors"
description: "Solutions for common CLI error messages"
keywords: [cli, errors, troubleshooting, solutions]
---

# Common CLI Errors

Solutions for frequently encountered CLI errors.

## Error: "Invalid API key"

**Problem**: API key is incorrect or revoked.

**Solution**:
```bash
# Verify API key
trace config get api-key

# Update API key
trace config set api-key rtm_live_abc123...

# Test
trace health
```

## Error: "Project not found"

**Problem**: Project ID doesn't exist or you don't have access.

**Solution**:
```bash
# List available projects
trace project list

# Switch to valid project
trace project switch "Project Name"
```

## Error: "Rate limit exceeded"

**Problem**: Too many API requests.

**Solution**:
```bash
# Wait and retry
# Or upgrade plan for higher limits
```

## Error: "Command not found"

**Problem**: CLI not installed or not in PATH.

**Solution**:
```bash
# Reinstall
pip3 install tracertm-cli

# Add to PATH
export PATH="$HOME/.local/bin:$PATH"
```

## Error: "Invalid JSON"

**Problem**: Invalid JSON in command arguments.

**Solution**:
```bash
# Validate JSON
echo '{"key": "value"}' | jq .

# Use proper JSON syntax
trace item create --metadata '{"priority": "high"}'
```

## Related Documentation

- [Troubleshooting](./06-troubleshooting) - General troubleshooting
- [Debug Mode](./06b-debug-mode) - Debug logging
