Juicebox Incident Runbook
Overview
Incident response procedures for Juicebox AI analysis platform integration failures. Covers analysis timeouts, dataset corruption, quota exhaustion, and export failures. Juicebox powers AI-driven people search and candidate analysis, so incidents disrupt recruiting pipelines, talent intelligence workflows, and automated sourcing. Classify severity immediately using the matrix below and follow the corresponding playbook.
Severity Levels
| Level | Definition | Response Time | Example |
|---|
| P1 - Critical | Full API outage or dataset corruption | 15 min | Health endpoint returns 5xx, analysis results missing |
| P2 - High | Analysis timeouts or export failures | 30 min | Search queries hang beyond 30s, CSV exports fail |
| P3 - Medium | Quota exhaustion or rate limiting | 2 hours | 429 responses, account quota at 100% usage |
| P4 - Low | Partial data or degraded result quality | 8 hours | Search returns fewer results than expected |
Diagnostic Steps
# Check API health
curl -s -o /dev/null -w "HTTP %{http_code}\n" \
-H "Authorization: Bearer $JUICEBOX_API_KEY" \
https://api.juicebox.ai/v1/health
# Check account quota usage
curl -s -H "Authorization: Bearer $JUICEBOX_API_KEY" \
https://api.juicebox.ai/v1/account/quota | jq '.used, .limit, .remaining'
# Test a minimal search request
curl -s -w "\nHTTP %{http_code}\n" \
-H "Authorization: Bearer $JUICEBOX_API_KEY" \
-H "Content-Type: application/json" \
-X POST https://api.juicebox.ai/v1/search \
-d '{"query": "software engineer", "limit": 1}'