Incident response runbook for Gamma integration issues.
Use when experiencing production incidents, outages,
or need systematic troubleshooting procedures.
Trigger with phrases like "gamma incident", "gamma outage",
"gamma down", "gamma emergency", "gamma runbook".
curl -X POST http://localhost:8080/admin/circuit-breaker \
-d '{"service": "gamma", "state": "open"}'
Long-term: Review rate limit tier with Gamma
Scenario 3: High Latency
Symptoms:
Slow presentation creation
Timeouts in logs
P95 latency > 10s
Actions:
Check Gamma latency vs our latency:
# Direct Gamma latency
for i in {1..5}; do
curl -w "%{time_total}\n" -o /dev/null -s \
-H "Authorization: Bearer $GAMMA_API_KEY" \
https://api.gamma.app/v1/ping
done
If Gamma is slow:
Increase timeouts temporarily
Enable async mode for non-critical operations
Queue heavy operations
If our infrastructure is slow:
Check CPU/memory on app servers
Review connection pool settings
Check network connectivity
Scenario 4: Authentication Failures (401/403)
Symptoms:
All requests failing with 401
"Invalid API key" errors
Sudden authentication failures
Actions:
Verify API key:
# Test key directly
curl -H "Authorization: Bearer $GAMMA_API_KEY" \
https://api.gamma.app/v1/ping
# Check key format
echo $GAMMA_API_KEY | head -c 20
If key is invalid:
Check if key was rotated
Deploy backup key: GAMMA_API_KEY_SECONDARY
Generate new key in Gamma dashboard
Notify team and update secrets
Communication Templates
Internal Notification
INCIDENT: Gamma Integration Issue
Severity: P[X]
Status: Investigating / Identified / Mitigating / Resolved
Impact: [Description of user impact]
Start Time: [ISO timestamp]
Summary: [Brief description]
Current Actions:
- [Action 1]
- [Action 2]
Next Update: [Time]
User-Facing Message
We're currently experiencing issues with presentation generation.
Our team is actively working to resolve this.
Workaround: [If available]
Status updates: [Link to status page]
ETA: [If known]