Skip to main content 홈 크리에이터 jeremylongshore tons-of-skills-marketplace documenso-incident-runbook
documenso-incident-runbook Manage incident response for Documenso integration issues.
Use when diagnosing production incidents, handling outages,
or responding to Documenso service disruptions.
Trigger with phrases like "documenso incident", "documenso outage",
"documenso down", "documenso troubleshooting".
설치로 이동 Skills Marketplace 커뮤니티가 만든 AI 스킬을 발견하고 탐색하세요.
Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.
직접 명령은 검토 Prompt를 거치지 않습니다. 실행하기 전에 소스를 확인하세요.
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace --skill documenso-incident-runbook명령은 한 줄로 유지됩니다. 복사하기 전에 가로로 스크롤해 전체 내용을 확인하세요.
로컬 사본을 원하시나요? SkillsMP에서 현재 제공할 수 있는 파일을 다운로드하세요.
Zip 다운로드 다운로드 중... 이 저장소의 다른 Skills langchain-deploy-integration Deploy a LangChain 1.0 / LangGraph 1.0 app to Cloud Run, Vercel, or LangServe correctly — with timeouts sized for chain length, cold-start mitigation, SSE anti-buffering headers, and Secret Manager over .env. Use when prepping a first production deploy, debugging a stream that hangs behind a proxy, or diagnosing p99 latency spikes. Trigger with "langchain deploy", "langchain cloud run", "langchain vercel python", "langchain langserve", or "langchain docker".
langchain-langgraph-agents Build a correct LangGraph 1.0 ReAct agent with create_react_agent — typed tools, error propagation, recursion caps, and stop conditions that actually stop. Use when writing a first tool-calling agent, migrating from AgentExecutor or initialize_agent, or diagnosing an agent that loops on vague prompts. Trigger with "langgraph agent", "create_react_agent", "langgraph tool calling", "AgentExecutor migration", or "agent loop cost".
langchain-langgraph-human-in-loop Build LangGraph 1.0 human-in-the-loop approval flows with interrupt_before /
interrupt_after and Command(resume=...) — JSON-serializable state, clean
resume semantics, and UI wiring for approval decisions. Use when adding an
approval gate before an expensive tool call, wiring a Slack/web UI for agent
approvals, or debugging a graph that crashes on interrupt.
Trigger with "langgraph human in loop", "langgraph interrupt_before",
"langgraph approval flow", "Command resume", "langgraph HITL".
name documenso-incident-runbook description Manage incident response for Documenso integration issues.
Use when diagnosing production incidents, handling outages,
or responding to Documenso service disruptions.
Trigger with phrases like "documenso incident", "documenso outage",
"documenso down", "documenso troubleshooting".
allowed-tools Read, Bash(curl:*), Bash(kubectl:*), Grep version 1.13.0 license MIT author Jeremy Longshore <jeremy@intentsolutions.io> tags ["saas","documenso","incident-response"] compatibility Designed for Claude Code
Documenso Incident Runbook
Overview
Step-by-step procedures for responding to Documenso integration incidents. Covers cloud outages, self-hosted issues, and integration failures.
Prerequisites
Access to monitoring dashboards
Documenso dashboard access
Application log access
On-call escalation contacts defined
Severity Levels
Level Description Examples Response Time P1 Complete signing outage All API calls failing, no documents can be sent < 15 min P2 Degraded functionality Slow responses, intermittent errors, webhooks delayed < 1 hour P3 Minor issue, workaround available Single document stuck, UI glitch < 4 hours P4 Non-urgent Feature request, documentation gap Next business day
Quick Diagnostic Commands
#!/bin/bash
set -euo pipefail
echo "=== Documenso Incident Diagnostic ==="
echo "--- Cloud Status ---"
curl -s https://status.documenso.com/api/v2/status.json 2>/dev/null | jq '.status' || echo "Status page unreachable"
echo "--- API Connectivity ---"
BASE="${DOCUMENSO_BASE_URL:-https://app.documenso.com/api/v1} "
HTTP_CODE=$(curl -s -o /dev/null -w "%{http_code}" \
-H "Authorization: Bearer $DOCUMENSO_API_KEY " \
"$BASE /documents?page=1&perPage=1" 2>/dev/null || echo "000" )
echo "API Status: $HTTP_CODE "
echo
"--- Latency Check ---"
for
in
seq
do
"%{time_total}"
"Authorization: Bearer $DOCUMENSO_API_KEY "
"$BASE /documents?page=1&perPage=1"
echo
"timeout"
echo
" Request $i : ${LATENCY} s"
done
echo
"--- Self-Hosted Container (if applicable) ---"
"name=documenso"
"{{.Names}}: {{.Status}}"
echo
"Docker not available or Documenso not self-hosted"
Incident Response Procedures
Scenario 1: Documenso Cloud Outage (5xx Errors) Symptoms: High error rate, 500/502/503 from Documenso API.
Check status page: https://status.documenso.com
If Documenso confirms outage:
Enable degraded mode in your app
Queue signing requests for later
Show user-facing message: "Document signing temporarily unavailable"
Monitor status page for resolution
If Documenso shows operational but you see errors:
Check your API key validity (could be rotated/revoked)
Check if specific endpoints fail (documents vs templates)
Review recent deployments for breaking changes
Contact Documenso support with diagnostic output
Scenario 2: Self-Hosted Database Issues Symptoms: Container running but API returns errors, migrations failing.
docker exec documenso-db pg_isready -U documenso
docker logs documenso --tail 100 | grep -i "error\|fatal\|prisma"
docker logs documenso --tail 50 | grep "prisma migrate"
docker exec documenso curl -s http://localhost:3000/api/health || echo "Internal health check failed"
Scenario 3: Webhook Delivery Failures Symptoms: Webhooks not arriving, document events not triggering workflows.
Checklist:
1. Verify webhook is enabled in Team Settings > Webhooks
2. Check your endpoint is returning 200 within 10 seconds
3. Verify HTTPS is working (Documenso won't send to HTTP)
4. Check X-Documenso-Secret matches your stored secret
5. Review your webhook handler logs for exceptions
6. If using ngrok: confirm tunnel is active
Scenario 4: Signing Certificate Expired (Self-Hosted) Symptoms: Documents can be sent but signatures are invalid or rejected by verification tools.
openssl pkcs12 -in /path/to/signing-cert.p12 -nokeys -passin pass:$CERT_PASSPHRASE | openssl x509 -noout -dates
Emergency Circuit Breaker
class DocumensoCircuitBreaker {
private isOpen = false ;
private openedAt = 0 ;
private readonly cooldownMs = 60000 ;
open (reason : string this .isOpen = true ;
this .openedAt = Date .now ();
console .error (`CIRCUIT BREAKER OPEN: ${reason} ` );
}
close (this .isOpen = false ;
console .log ("Circuit breaker closed — Documenso operations resumed" );
}
async execute<T>(fn : () => Promise <T>, fallback ?: () => T): Promise <T> {
if (this .isOpen ) {
if (Date .now () - this .openedAt > this .cooldownMs ) {
try {
const result = await fn ();
this .close ();
return result;
} catch {
this .openedAt = Date .now ();
if (fallback) return fallback ();
throw new Error ("Documenso unavailable — circuit breaker open" );
}
}
if (fallback) return fallback ();
throw new Error ("Documenso unavailable — circuit breaker open" );
}
return fn ();
}
}
Post-Incident Checklist
Communication Template INCIDENT: Documenso Integration Issue
Severity: P[X]
Status: Investigating | Identified | Mitigating | Resolved
Impact: [Number of users/documents affected]
Start: [ISO timestamp]
Summary: [Brief description]
Timeline:
- [HH:MM] Issue detected via [monitoring/user report]
- [HH:MM] Root cause identified: [cause]
- [HH:MM] Fix deployed / workaround applied
- [HH:MM] Resolved, monitoring for recurrence
Action Items:
- [ ] [Preventive measure 1]
- [ ] [Preventive measure 2]
Error Handling Issue Cause Solution Persistent 5xx Documenso outage Enable circuit breaker, queue requests Self-hosted crash loop Bad migration or config Check docker logs, rollback image Certificate invalid Expired or wrong cert Replace .p12 file, restart container All webhooks failing Endpoint down Check HTTPS endpoint, verify health
Resources
Next Steps For data handling procedures, see documenso-data-handling.
