Skip to content
Back to skills

Shopify Incident Runbook

ASecurity

'Execute Shopify incident response with triage using Shopify status page,

  • 2,719 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 21, 2026
ai-agentsbashapi

Works with

  • claude code
  • api

Security analysis

A100/100

Pro scans all 3 files and shows the line behind each finding

Scanned September 21, 2026

npx -y skills add jeremylongshore/claude-code-plugins-plus --skill shopify-incident-runbook --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Shopify Incident Runbook?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Shopify Incident Runbook
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/jeremylongshore-shopify-incident-runbook-887aa77d/badge)](https://www.skillsdirectory.com/skills/jeremylongshore-shopify-incident-runbook-887aa77d)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: shopify-incident-runbook
description: 'Execute Shopify incident response with triage using Shopify status page,

  API health checks, and rate limit diagnosis.

  Use when a Shopify integration is down, returning errors, or behaving unexpectedly
  in production.

  Trigger with phrases like "shopify incident", "shopify outage",

  "shopify down", "shopify on-call", "shopify emergency", "shopify not responding".

  '
allowed-tools: Read, Grep, Bash(curl:*)
version: 2.7.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
tags:
- saas
- ecommerce
- shopify
compatibility: Designed for Claude Code
---
# Shopify Incident Runbook

## Overview

Rapid incident response for Shopify API outages, authentication failures, and rate limit emergencies. Distinguish between Shopify-side issues and your app's integration issues.

## Prerequisites

- Access to Shopify admin and status page
- Application logs and metrics
- Communication channels (Slack, PagerDuty)

## Instructions

### Step 1: Quick Triage (First 5 Minutes)

Run the triage script to check Shopify status, API connectivity, REST rate limits, and GraphQL throttle state in one pass.

See [Triage Script](references/triage-script.md) for the complete diagnostic script.

### Step 2: Decision Tree

```
Is Shopifystatus.com showing an incident?
├── YES → Shopify-side outage
│   ├── Enable graceful degradation / cached responses
│   ├── Notify stakeholders: "Shopify is experiencing issues"
│   └── Monitor status page for resolution
│
└── NO → Likely your integration
    ├── HTTP 401? → Token expired or revoked
    │   └── Check: Was app reinstalled? Rotate token.
    ├── HTTP 403? → Scope missing
    │   └── Check: Were scopes changed? Re-run OAuth.
    ├── HTTP 429 / THROTTLED? → Rate limit exceeded
    │   └── Check: Runaway loop? Reduce query frequency.
    ├── HTTP 5xx? → Intermittent Shopify issue
    │   └── Retry with backoff, monitor for pattern.
    └── Network timeout? → Infrastructure issue
        └── Check: DNS, firewall, TLS certificates.
```

### Step 3: Immediate Actions by Error Type

Diagnostic commands and remediation for 401 (token expired), 429 (rate limited), and 5xx (Shopify internal errors). Always capture `X-Request-Id` headers for Shopify support.

See [Error Type Actions](references/error-type-actions.md) for complete commands per error type.

### Step 4: Communication Templates

**Internal (Slack):**

```
INCIDENT: Shopify Integration Issue
Severity: P[1/2/3]
Status: INVESTIGATING
Impact: [What users/merchants are affected]
Root cause: [Shopify outage / Our auth issue / Rate limiting]
Action: [What we're doing now]
Next update: [Time]
Responder: @[name]
```

**External (Merchant-facing):**

```
We're currently experiencing issues with some Shopify-connected features.
[Order sync / Product updates / etc.] may be delayed.
We're actively working on resolution and will update shortly.
All data is safe — no orders or products have been lost.
```

## Output

- Triage completed within 5 minutes
- Root cause identified (Shopify vs. integration)
- Immediate mitigation applied
- Stakeholders notified

## Error Handling

| Scenario | Response Time | Escalation |
|----------|--------------|------------|
| Shopify API fully down | Monitor status page | Nothing to fix on our side |
| Auth token revoked | < 15 min | Trigger re-auth, notify merchant |
| Rate limit exhaustion | < 30 min | Reduce query frequency, optimize costs |
| Webhook delivery failures | < 1 hour | Check endpoint health, review HMAC |
| Data sync stalled | < 4 hours | Run manual sync after resolution |

## Examples

### One-Liner Health Check

```bash
curl -sf -H "X-Shopify-Access-Token: $SHOPIFY_ACCESS_TOKEN" \
  "https://$SHOPIFY_STORE/admin/api/${SHOPIFY_API_VERSION:-2025-04}/shop.json" \
  | jq '{name: .shop.name, plan: .shop.plan_name}' \
  && echo "SHOPIFY: HEALTHY" || echo "SHOPIFY: UNREACHABLE"
```

### Post-Incident Checklist

- [ ] Timeline documented with UTC timestamps
- [ ] Root cause identified
- [ ] `X-Request-Id` values collected (for Shopify support)
- [ ] Customer impact assessed
- [ ] Prevention action items created
- [ ] Monitoring/alerting gaps identified

## Resources

- [Shopify Status Page](https://www.shopifystatus.com)
- [Shopify Partner Support](https://help.shopify.com/en/partners)
- [Shopify Community Forums](https://community.shopify.dev)

Files in this skill

  • SKILL.md4.4 KB
  • references/error-type-actions.md1.3 KB
  • references/triage-script.md1.9 KB

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.