Production incident response procedures for Linear integrations.
Use when handling production issues, diagnosing outages,
or responding to Linear-related incidents.
Trigger: "linear incident", "linear outage", "linear production issue",
"debug linear production", "linear down", "linear 500".
Production incident response procedures for Linear integrations.
Use when handling production issues, diagnosing outages,
or responding to Linear-related incidents.
Trigger: "linear incident", "linear outage", "linear production issue",
"debug linear production", "linear down", "linear 500".
allowed-tools
Read, Write, Edit, Bash(curl:*), Grep
version
1.12.0
license
MIT
author
Jeremy Longshore <jeremy@intentsolutions.io>
tags
["saas","linear","debugging","incident-response"]
compatibility
Designed for Claude Code, also compatible with Codex and OpenClaw
Linear Incident Runbook
Overview
Step-by-step runbooks for handling production incidents with Linear integrations. Covers API authentication failures, rate limiting, webhook issues, and Linear platform outages.
Incident Classification
Severity
Impact
Response
Examples
SEV1
Complete integration outage
< 15 min
Auth broken, API unreachable
SEV2
Major degradation
< 30 min
High error rate, rate limited
SEV3
Minor issues
< 2 hours
Some features affected
SEV4
Low impact
< 24 hours
Warnings, non-critical
Immediate Actions (All Incidents)
Step 1: Confirm the Issue
set -euo pipefail
# 1. Check Linear platform status
curl -s https://status.linear.app/api/v2/status.json | jq '.status'# 2. Test your API key
curl -s -X POST https://api.linear.app/graphql \
-H "Authorization: $LINEAR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"query": "{ viewer { name email } }"}' | jq .
# 3. Check rate limit status
curl -s -I -X POST https://api.linear.app/graphql \
-H "Authorization: $LINEAR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"query": "{ viewer { id } }"}' 2>&1 | grep -i ratelimit
# 4. Check your app health endpoint
curl -s https://yourapp.com/health/linear | jq .