| name | perplexity-common-errors |
| description | Diagnose and fix Perplexity common errors and exceptions.
Use when encountering Perplexity errors, debugging failed requests,
or troubleshooting integration issues.
Trigger with phrases like "perplexity error", "fix perplexity",
"perplexity not working", "debug perplexity".
|
| allowed-tools | Read, Grep, Bash(curl:*) |
| version | 1.0.0 |
| license | MIT |
| author | Jeremy Longshore <jeremy@intentsolutions.io> |
Perplexity Common Errors
Overview
Quick reference for the top 10 most common Perplexity errors and their solutions.
Prerequisites
- Perplexity 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:
echo $PERPLEXITY_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 perplexity-rate-limits skill.
Network Timeout
Error Message:
Request timeout after 30000ms
Cause: Network connectivity or server latency issues.
Solution:
const client = new Client({ timeout: 60000 });
Examples
Quick Diagnostic Commands
curl -s https://status.perplexity.com
curl -I https://api.perplexity.com
env | grep PERPLEXITY
Escalation Path
- Collect evidence with
perplexity-debug-bundle
- Check Perplexity status page
- Contact support with request ID
Resources
Next Steps
For comprehensive debugging, see perplexity-debug-bundle.
