Skip to main content

Common Errors

Solutions to frequent issues when using Reeva.

Authentication Errors​

"Invalid or expired token"​

Error: 401 Unauthorized

Causes:

  • JWT token expired (>1 hour old)
  • API key revoked or invalid
  • Extra spaces in key/token

Solutions:

  1. For JWT: Get fresh token from Firebase Auth
  2. For API key:
    • Verify key in dashboard (not revoked)
    • Check for typos/spaces
    • Generate new key if needed
  3. Ensure Authorization: Bearer prefix is included

"Forbidden - Access denied"​

Error: 403 Forbidden

Causes:

  • Trying to access someone else's resource
  • API key not linked to server
  • Insufficient permissions

Solutions:

  • Verify you own the server/tool
  • Check API key is linked (for global keys)
  • Use correct server ID

Credit Errors​

"Insufficient credits"​

Error: Tool execution blocked

Message: "Required: 3, Available: 1"

Solutions:

  1. Check balance: Dashboard → Usage
  2. Purchase credits: Click balance → Buy Credits
  3. Verify tool actually requires credits (check docs)

"Credit deduction failed"​

Error: Internal server error during deduction

Solutions:

  • Retry request (credits not deducted)
  • Contact support if persists
  • Check service status page

Tool Execution Errors​

"Tool not found"​

Error: 404 Not Found

Causes:

  • Tool name misspelled
  • Custom tool deleted
  • Tool not added to server

Solutions:

  1. Check spelling: google_search not google search
  2. Verify custom tool exists: Dashboard → Tools → My Tools
  3. Confirm tool added to server: Servers → Your Server → Tools

"Invalid parameters"​

Error: 400 Bad Request

Causes:

  • Required parameter missing
  • Wrong data type
  • Invalid value

Solutions:

  1. Check tool's input schema: Docs → Tools → [Tool Name]
  2. Verify all required params provided
  3. Ensure correct types (string, number, boolean, array)
  4. Test in Playground to see detailed error

"External API error"​

Error: Tool execution failed

Causes:

  • External service (Notion, Jira, etc.) is down
  • Invalid credentials
  • Rate limit hit

Solutions:

  1. Check external service status
  2. Verify credentials in Accounts page
  3. Wait and retry (rate limits reset)
  4. Check credential permissions

Server Errors​

"Server not found"​

Error: 404 Not Found

Causes:

  • Server ID incorrect
  • Server deleted
  • Wrong environment (dev vs prod)

Solutions:

  • Verify server ID from dashboard
  • Check server still exists (not deleted)
  • Confirm using correct API endpoint

"No tools in server"​

Error: Server has no tools to list/call

Causes:

  • No custom tools added to server
  • All custom tools deleted

Solutions:

  1. Dashboard → Servers → Your Server
  2. Click "Edit"
  3. Add custom tools
  4. Save and retry

Credential Errors​

"Credentials not found"​

Error: Tool requires credentials but none provided

Causes:

  • No account linked
  • Account deleted
  • Wrong service type

Solutions:

  1. Dashboard → Accounts
  2. Add account for required service (e.g., Notion)
  3. Link to custom tool
  4. Or add to server's service_credentials

"Authentication failed with external service"​

Error: 401/403 from Notion, Jira, etc.

Causes:

  • Expired OAuth token
  • Revoked API key
  • Insufficient permissions

Solutions:

  1. Re-authenticate account (OAuth)
  2. Generate new API key in external service
  3. Update credentials in Reeva
  4. Check permissions granted

Network Errors​

"Connection timeout"​

Error: Request took too long

Causes:

  • Network issues
  • External service slow
  • Large data transfer

Solutions:

  • Retry request
  • Check internet connection
  • Use pagination for large datasets
  • Contact support if consistent

"Rate limit exceeded"​

Error: 429 Too Many Requests

Causes:

  • Too many requests too quickly
  • Hitting Reeva rate limits
  • External service rate limits

Solutions:

  • Wait and retry (limits reset)
  • Implement backoff strategy
  • Spread requests over time
  • Consider upgrading plan (if Reeva limit)

MCP Protocol Errors​

"Invalid JSON-RPC request"​

Error: 400 Bad Request

Causes:

  • Malformed JSON
  • Missing required fields
  • Wrong method name

Solutions:

  1. Validate JSON syntax
  2. Include: jsonrpc: "2.0", method, id
  3. Use correct method: tools/list, tools/call, etc.
  4. See MCP Protocol docs

"Method not supported"​

Error: 501 Not Implemented

Causes:

  • Using unsupported MCP method
  • Typo in method name

Solutions:

  • Supported methods: tools/list, tools/call, initialize, ping
  • Check spelling
  • See MCP Protocol reference

IDE Integration Errors​

Server won't connect​

See detailed troubleshooting: IDE Integration Troubleshooting

Quick checks:

  • ✅ API key correct?
  • ✅ Server ID correct?
  • ✅ IDE restarted?
  • ✅ Valid JSON config?

Getting Help​

Debug Checklist​

Before contacting support:

  • Checked error message carefully
  • Searched this page for error
  • Verified credentials/API keys
  • Tested in Playground (if tool issue)
  • Checked service status
  • Tried with different tool/server

Contact Support​

Include:

  • Error message (exact text)
  • Server ID (if relevant)
  • Tool name (if relevant)
  • Timestamp of error
  • Steps to reproduce
  • Screenshots (if helpful)

See Also​