clay-common-errors

Diagnose and fix Clay common errors and exceptions.Use when encountering Clay errors, debugging failed requests,or troubleshooting integration issues.Trigger with phrases like "clay error", "fix clay","clay not working", "debug clay".

⭐939stars🔀114forks📁View on GitHub🕐Updated Jan 11, 2026⬇️2downloads

When & Why to Use This Skill

This Claude skill provides a comprehensive diagnostic framework for identifying and resolving the most common errors within the Clay ecosystem. It offers step-by-step troubleshooting guides, actionable code fixes, and connectivity checks to minimize downtime and optimize integration performance for developers and data teams.

Use Cases

  • Case 1: Troubleshooting authentication failures by verifying API keys and local environment configurations.
  • Case 2: Managing API rate limits through the implementation of exponential backoff and retry logic.
  • Case 3: Resolving network latency and timeout issues by optimizing client-side timeout settings and monitoring service status.
  • Case 4: Debugging failed integration requests using automated diagnostic commands and status checks to identify root causes quickly.
nameclay-common-errors
description|
allowed-toolsRead, Grep, Bash(curl:*)
version1.0.0
licenseMIT
authorJeremy Longshore <jeremy@intentsolutions.io>

Clay Common Errors

Overview

Quick reference for the top 10 most common Clay errors and their solutions.

Prerequisites

  • Clay SDK installed
  • API credentials configured
  • Access to error logs

Instructions

Step 1: Identify the Error

Check error message and code in your logs or console.

Step 2: Find Matching Error Below

Match your error to one of the documented cases.

Step 3: Apply Solution

Follow the solution steps for your specific error.

Output

  • Identified error cause
  • Applied fix
  • Verified resolution

Error Handling

Authentication Failed

Error Message:

Authentication error: Invalid API key

Cause: API key is missing, expired, or invalid.

Solution:

# Verify API key is set
echo $CLAY_API_KEY

Rate Limit Exceeded

Error Message:

Rate limit exceeded. Please retry after X seconds.

Cause: Too many requests in a short period.

Solution: Implement exponential backoff. See clay-rate-limits skill.


Network Timeout

Error Message:

Request timeout after 30000ms

Cause: Network connectivity or server latency issues.

Solution:

// Increase timeout
const client = new Client({ timeout: 60000 });

Examples

Quick Diagnostic Commands

# Check Clay status
curl -s https://status.clay.com

# Verify API connectivity
curl -I https://api.clay.com

# Check local configuration
env | grep CLAY

Escalation Path

  1. Collect evidence with clay-debug-bundle
  2. Check Clay status page
  3. Contact support with request ID

Resources

Next Steps

For comprehensive debugging, see clay-debug-bundle.