salesforce-common-errors

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

claude-code
3 Tools
salesforce-pack Plugin
saas packs Category

Allowed Tools

ReadGrepBash(curl:*)

Provided by Plugin

salesforce-pack

Claude Code skill pack for Salesforce (30 skills)

saas packs v1.0.0
View Plugin

Installation

This skill is included in the salesforce-pack plugin:

/plugin install salesforce-pack@claude-code-plugins-plus

Click to copy

Instructions

Salesforce Common Errors

Overview

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

Prerequisites

  • Salesforce 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 $SALESFORCE_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 salesforce-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 Salesforce status
curl -s https://status.salesforce.com

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

# Check local configuration
env | grep SALESFORCE

Escalation Path

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

Resources

Next Steps

For comprehensive debugging, see salesforce-debug-bundle.

Ready to use salesforce-pack?