[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78Z4WMYRPCRMPFTRNXFMWM9":3,"skill-same:01M78Z4WMYRPCRMPFTRNXFMWM9":57},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":34,"commitSha":35,"skillDirectory":36,"forksCount":37,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":40,"ownerDescription":41,"updatedAt":42,"install":43,"resources":56},"01M78Z4WMYRPCRMPFTRNXFMWM9","customerio-advanced-troubleshooting",null,"Apply Customer.io advanced debugging and incident response.\nUse when diagnosing complex delivery issues, investigating\ncampaign failures, or running incident playbooks.\nTrigger: \"debug customer.io\", \"customer.io investigation\",\n\"customer.io troubleshoot\", \"customer.io incident\", \"customer.io not delivering\".","jukeyman\u002Fjukeyman-skills","jukeyman","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F142960420?v=4","01M78FR4Y3DHMMCBCC0GXXNB3F","RICK JEFFERSON","01M78FR4Z8RVQRAD31Y5J7V6EB",1,"MIT","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--customerio-pack--customerio-advanced-troubleshooting\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: customerio-advanced-troubleshooting\ndescription: |\n  Apply Customer.io advanced debugging and incident response.\n  Use when diagnosing complex delivery issues, investigating\n  campaign failures, or running incident playbooks.\n  Trigger: \"debug customer.io\", \"customer.io investigation\",\n  \"customer.io troubleshoot\", \"customer.io incident\", \"customer.io not delivering\".\nallowed-tools: Read, Write, Edit, Bash(curl:*), Bash(npx:*), Glob, Grep\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\ntags: [saas, customer-io, debugging, incident-response]\n---\n# Customer.io Advanced Troubleshooting\n\n## Overview\n\nAdvanced debugging techniques for complex Customer.io issues: systematic investigation framework, API debug client, user profile analysis, campaign\u002Fbroadcast debugging, network diagnostics, and incident response runbooks.\n\n## Prerequisites\n\n- Access to Customer.io dashboard (admin recommended)\n- Application logs access\n- `curl` for API testing\n\n## Troubleshooting Framework\n\nFor every issue, answer these five questions first:\n\n1. **What** is the expected vs actual behavior?\n2. **When** did the issue start? (Check deploy history, CIO status page)\n3. **Who** is affected — one user, a segment, or everyone?\n4. **Where** in the pipeline — API call, delivery, or rendering?\n5. **How** often — every time, intermittent, or one-time?\n\n## Instructions\n\n### Step 1: API Debug Client\n\n```typescript\n\u002F\u002F lib\u002Fcustomerio-debug.ts\nimport { TrackClient, APIClient, RegionUS } from \"customerio-node\";\n\nexport class DebugCioClient {\n  private track: TrackClient;\n\n  constructor() {\n    this.track = new TrackClient(\n      process.env.CUSTOMERIO_SITE_ID!,\n      process.env.CUSTOMERIO_TRACK_API_KEY!,\n      { region: RegionUS }\n    );\n  }\n\n  async debugIdentify(userId: string, attrs: Record\u003Cstring, any>) {\n    console.log(`\\n--- Debug: identify(\"${userId}\") ---`);\n    console.log(\"Attributes:\", JSON.stringify(attrs, null, 2));\n\n    const start = Date.now();\n    try {\n      await this.track.identify(userId, attrs);\n      const latency = Date.now() - start;\n      console.log(`Result: SUCCESS (${latency}ms)`);\n      return { success: true, latency };\n    } catch (err: any) {\n      const latency = Date.now() - start;\n      console.log(`Result: FAILED (${latency}ms)`);\n      console.log(`Status: ${err.statusCode}`);\n      console.log(`Message: ${err.message}`);\n      console.log(`Body: ${JSON.stringify(err.body ?? err.response)}`);\n      return { success: false, latency, statusCode: err.statusCode, message: err.message };\n    }\n  }\n\n  async debugTrack(userId: string, name: string, data?: any) {\n    console.log(`\\n--- Debug: track(\"${userId}\", \"${name}\") ---`);\n    console.log(\"Data:\", JSON.stringify(data, null, 2));\n\n    const start = Date.now();\n    try {\n      await this.track.track(userId, { name, data });\n      const latency = Date.now() - start;\n      console.log(`Result: SUCCESS (${latency}ms)`);\n      return { success: true, latency };\n    } catch (err: any) {\n      const latency = Date.now() - start;\n      console.log(`Result: FAILED (${latency}ms)`);\n      console.log(`Status: ${err.statusCode}`);\n      console.log(`Message: ${err.message}`);\n      return { success: false, latency, statusCode: err.statusCode };\n    }\n  }\n}\n```\n\n### Step 2: User Investigation Script\n\n```bash\n#!\u002Fusr\u002Fbin\u002Fenv bash\nset -euo pipefail\n# scripts\u002Finvestigate-user.sh \u003Cuser-id>\n\nUSER_ID=\"${1:?Usage: investigate-user.sh \u003Cuser-id>}\"\nSITE_ID=\"${CUSTOMERIO_SITE_ID:?Missing CUSTOMERIO_SITE_ID}\"\nAPI_KEY=\"${CUSTOMERIO_TRACK_API_KEY:?Missing CUSTOMERIO_TRACK_API_KEY}\"\n\necho \"=== Investigating User: ${USER_ID} ===\"\necho \"\"\n\n# 1. Check if user exists (try to identify with minimal data)\necho \"--- API Connectivity Test ---\"\nHTTP_CODE=$(curl -s -o \u002Fdev\u002Fnull -w \"%{http_code}\" \\\n  -u \"${SITE_ID}:${API_KEY}\" \\\n  -X PUT \"https:\u002F\u002Ftrack.customer.io\u002Fapi\u002Fv1\u002Fcustomers\u002F${USER_ID}\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"_debug_check\":\"true\"}')\necho \"Track API for user: HTTP ${HTTP_CODE}\"\n\necho \"\"\necho \"--- Dashboard Checklist ---\"\necho \"Check the following in Customer.io dashboard:\"\necho \"1. People > Search '${USER_ID}'\"\necho \"   - Does profile exist?\"\necho \"   - Does it have an email attribute?\"\necho \"   - Is there a 'Suppressed' badge?\"\necho \"\"\necho \"2. Activity tab:\"\necho \"   - Are events being received?\"\necho \"   - Any bounce\u002Fcomplaint events?\"\necho \"   - Last identify timestamp correct?\"\necho \"\"\necho \"3. Segments tab:\"\necho \"   - Which segments does user belong to?\"\necho \"   - Does segment match campaign audience?\"\necho \"\"\necho \"4. Campaigns > Find relevant campaign:\"\necho \"   - Is campaign status Active?\"\necho \"   - Does trigger event match?\"\necho \"   - Check 'Messages' tab for delivery attempts\"\n```\n\n### Step 3: Campaign Debugging\n\nCommon campaign issues and their investigation path:\n\n| Symptom | Check First | Then Check |\n|---------|------------|------------|\n| Campaign not triggering | Event name match (case-sensitive) | Campaign status (Active?) |\n| User not matched | Segment conditions | User attributes match segment? |\n| Email not delivered | User has `email` attribute | Bounce\u002Fsuppression status |\n| Liquid template broken | `message_data` has all required fields | Preview with real data in dashboard |\n| Wrong email content | Correct campaign version is Active | Template variables populated |\n| Delayed sends | Campaign \"Wait\" steps | Queue backlog in Customer.io |\n\n```typescript\n\u002F\u002F Programmatic campaign debug\nasync function debugCampaignTrigger(\n  userId: string,\n  eventName: string,\n  eventData: Record\u003Cstring, any>\n) {\n  const debug = new DebugCioClient();\n\n  console.log(\"=== Campaign Trigger Debug ===\\n\");\n\n  \u002F\u002F 1. Can we identify the user?\n  const identifyResult = await debug.debugIdentify(userId, {\n    _debug_campaign_check: true,\n  });\n\n  if (!identifyResult.success) {\n    console.log(\"\\nBLOCKER: Cannot identify user. Fix auth first.\");\n    return;\n  }\n\n  \u002F\u002F 2. Can we track the event?\n  const trackResult = await debug.debugTrack(userId, eventName, eventData);\n\n  if (!trackResult.success) {\n    console.log(\"\\nBLOCKER: Cannot track event. Check error above.\");\n    return;\n  }\n\n  console.log(\"\\n=== API Side OK ===\");\n  console.log(\"If campaign still not triggering, check in dashboard:\");\n  console.log(`1. Event name: \"${eventName}\" (must match exactly, case-sensitive)`);\n  console.log(\"2. Campaign status: must be Active (not Draft\u002FPaused)\");\n  console.log(\"3. Campaign audience: user must match segment\u002Ffilter\");\n  console.log(\"4. Campaign frequency: check if user already received\");\n  console.log(\"5. Suppression: check if user is suppressed\");\n}\n```\n\n### Step 4: Network Diagnostics\n\n```bash\n#!\u002Fusr\u002Fbin\u002Fenv bash\nset -euo pipefail\n# scripts\u002Fcio-network-diag.sh\n\necho \"=== Customer.io Network Diagnostics ===\"\necho \"\"\n\n# DNS resolution\necho \"--- DNS Resolution ---\"\nfor host in track.customer.io api.customer.io status.customer.io; do\n  IP=$(dig +short \"$host\" 2>\u002Fdev\u002Fnull | head -1)\n  echo \"${host}: ${IP:-FAILED}\"\ndone\n\necho \"\"\n\n# TLS check\necho \"--- TLS Certificate ---\"\necho | openssl s_client -connect track.customer.io:443 -servername track.customer.io 2>\u002Fdev\u002Fnull \\\n  | openssl x509 -noout -subject -issuer -dates 2>\u002Fdev\u002Fnull \\\n  || echo \"TLS check failed\"\n\necho \"\"\n\n# Latency test\necho \"--- Latency (5 samples) ---\"\nfor i in $(seq 1 5); do\n  LATENCY=$(curl -s -o \u002Fdev\u002Fnull -w \"%{time_total}\" \"https:\u002F\u002Ftrack.customer.io\")\n  echo \"Request ${i}: ${LATENCY}s\"\ndone\n\necho \"\"\n\n# Status page\necho \"--- Platform Status ---\"\ncurl -s \"https:\u002F\u002Fstatus.customer.io\u002Fapi\u002Fv2\u002Fstatus.json\" \\\n  | python3 -c \"import sys,json; d=json.load(sys.stdin); print(f'Status: {d[\\\"status\\\"][\\\"description\\\"]}')\" \\\n  2>\u002Fdev\u002Fnull || echo \"Could not fetch status\"\n```\n\n### Step 5: Incident Response Runbooks\n\n**P1 — Complete outage (all API calls failing):**\n1. Check https:\u002F\u002Fstatus.customer.io — is Customer.io down?\n2. If CIO is up: check your credentials (rotate if compromised)\n3. Enable circuit breaker to stop retries hitting a dead endpoint\n4. Switch to fallback queue (events stored in Redis\u002FKafka)\n5. Notify affected teams\n6. When restored: drain fallback queue, verify event delivery\n\n**P2 — High error rate (>5% failures):**\n1. Check error breakdown: which status codes?\n2. If 429: reduce concurrency, check rate limiter config\n3. If 5xx: check CIO status page, enable backoff\n4. If 401: credentials may have been rotated — check secrets manager\n5. Monitor error rate — escalate to P1 if not recovering\n\n**P3 — Delivery issues (messages not arriving):**\n1. Verify user has `email` attribute (People > user profile)\n2. Check suppression status (Suppressed badge)\n3. Check bounce history (Activity tab > filter bounces)\n4. Verify sending domain (Settings > Sending Domains)\n5. Check campaign is Active, trigger event matches\n6. Review spam folder and email headers\n\n**P4 — Webhook processing failures:**\n1. Verify webhook endpoint is publicly accessible\n2. Check signature verification (secret matches dashboard?)\n3. Review webhook event logs for parsing errors\n4. Check queue health if using async processing\n5. Verify Customer.io IP allowlist if using firewall\n\n## Diagnostic Commands\n\n```bash\n# Quick API health check\ncurl -s -u \"$CUSTOMERIO_SITE_ID:$CUSTOMERIO_TRACK_API_KEY\" \\\n  -X PUT \"https:\u002F\u002Ftrack.customer.io\u002Fapi\u002Fv1\u002Fcustomers\u002Fhealth-check\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"_diag\":true}' \\\n  -w \"\\nHTTP: %{http_code} Time: %{time_total}s\\n\"\n\n# Check App API\ncurl -s -H \"Authorization: Bearer $CUSTOMERIO_APP_API_KEY\" \\\n  \"https:\u002F\u002Fapi.customer.io\u002Fv1\u002Fcampaigns\" \\\n  -w \"\\nHTTP: %{http_code}\\n\" | head -5\n\n# Platform status\ncurl -s \"https:\u002F\u002Fstatus.customer.io\u002Fapi\u002Fv2\u002Fstatus.json\" | python3 -m json.tool\n```\n\n## Error Handling\n\n| Issue | Solution |\n|-------|----------|\n| Intermittent 5xx | Transient — retry with backoff handles it |\n| Consistent 401 after deploy | Credentials changed — check env vars and secrets |\n| User receiving duplicate messages | Event deduplication or campaign frequency cap |\n| Webhook events stop arriving | Check endpoint health, CIO IP allowlist, SSL cert validity |\n\n## Resources\n\n- [Customer.io Status Page](https:\u002F\u002Fstatus.customer.io\u002F)\n- [Customer.io Community](https:\u002F\u002Fcommunity.customer.io\u002F)\n- [Reporting Webhooks Reference](https:\u002F\u002Fdocs.customer.io\u002Fintegrations\u002Fapi\u002Fwebhooks\u002F)\n- [Troubleshooting Deliverability](https:\u002F\u002Fdocs.customer.io\u002Fjourneys\u002Fdeliverability\u002F)\n\n## Next Steps\n\nAfter troubleshooting, proceed to `customerio-reliability-patterns` for fault tolerance.\n","# Customer.io Advanced Troubleshooting\n\n## Overview\n\nAdvanced debugging techniques for complex Customer.io issues: systematic investigation framework, API debug client, user profile analysis, campaign\u002Fbroadcast debugging, network diagnostics, and incident response runbooks.\n\n## Prerequisites\n\n- Access to Customer.io dashboard (admin recommended)\n- Application logs access\n- `curl` for API testing\n\n## Troubleshooting Framework\n\nFor every issue, answer these five questions first:\n\n1. **What** is the expected vs actual behavior?\n2. **When** did the issue start? (Check deploy history, CIO status page)\n3. **Who** is affected — one user, a segment, or everyone?\n4. **Where** in the pipeline — API call, delivery, or rendering?\n5. **How** often — every time, intermittent, or one-time?\n\n## Instructions\n\n### Step 1: API Debug Client\n\n```typescript\n\u002F\u002F lib\u002Fcustomerio-debug.ts\nimport { TrackClient, APIClient, RegionUS } from \"customerio-node\";\n\nexport class DebugCioClient {\n  private track: TrackClient;\n\n  constructor() {\n    this.track = new TrackClient(\n      process.env.CUSTOMERIO_SITE_ID!,\n      process.env.CUSTOMERIO_TRACK_API_KEY!,\n      { region: RegionUS }\n    );\n  }\n\n  async debugIdentify(userId: string, attrs: Record\u003Cstring, any>) {\n    console.log(`\\n--- Debug: identify(\"${userId}\") ---`);\n    console.log(\"Attributes:\", JSON.stringify(attrs, null, 2));\n\n    const start = Date.now();\n    try {\n      await this.track.identify(userId, attrs);\n      const latency = Date.now() - start;\n      console.log(`Result: SUCCESS (${latency}ms)`);\n      return { success: true, latency };\n    } catch (err: any) {\n      const latency = Date.now() - start;\n      console.log(`Result: FAILED (${latency}ms)`);\n      console.log(`Status: ${err.statusCode}`);\n      console.log(`Message: ${err.message}`);\n      console.log(`Body: ${JSON.stringify(err.body ?? err.response)}`);\n      return { success: false, latency, statusCode: err.statusCode, message: err.message };\n    }\n  }\n\n  async debugTrack(userId: string, name: string, data?: any) {\n    console.log(`\\n--- Debug: track(\"${userId}\", \"${name}\") ---`);\n    console.log(\"Data:\", JSON.stringify(data, null, 2));\n\n    const start = Date.now();\n    try {\n      await this.track.track(userId, { name, data });\n      const latency = Date.now() - start;\n      console.log(`Result: SUCCESS (${latency}ms)`);\n      return { success: true, latency };\n    } catch (err: any) {\n      const latency = Date.now() - start;\n      console.log(`Result: FAILED (${latency}ms)`);\n      console.log(`Status: ${err.statusCode}`);\n      console.log(`Message: ${err.message}`);\n      return { success: false, latency, statusCode: err.statusCode };\n    }\n  }\n}\n```\n\n### Step 2: User Investigation Script\n\n```bash\n#!\u002Fusr\u002Fbin\u002Fenv bash\nset -euo pipefail\n# scripts\u002Finvestigate-user.sh \u003Cuser-id>\n\nUSER_ID=\"${1:?Usage: investigate-user.sh \u003Cuser-id>}\"\nSITE_ID=\"${CUSTOMERIO_SITE_ID:?Missing CUSTOMERIO_SITE_ID}\"\nAPI_KEY=\"${CUSTOMERIO_TRACK_API_KEY:?Missing CUSTOMERIO_TRACK_API_KEY}\"\n\necho \"=== Investigating User: ${USER_ID} ===\"\necho \"\"\n\n# 1. Check if user exists (try to identify with minimal data)\necho \"--- API Connectivity Test ---\"\nHTTP_CODE=$(curl -s -o \u002Fdev\u002Fnull -w \"%{http_code}\" \\\n  -u \"${SITE_ID}:${API_KEY}\" \\\n  -X PUT \"https:\u002F\u002Ftrack.customer.io\u002Fapi\u002Fv1\u002Fcustomers\u002F${USER_ID}\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"_debug_check\":\"true\"}')\necho \"Track API for user: HTTP ${HTTP_CODE}\"\n\necho \"\"\necho \"--- Dashboard Checklist ---\"\necho \"Check the following in Customer.io dashboard:\"\necho \"1. People > Search '${USER_ID}'\"\necho \"   - Does profile exist?\"\necho \"   - Does it have an email attribute?\"\necho \"   - Is there a 'Suppressed' badge?\"\necho \"\"\necho \"2. Activity tab:\"\necho \"   - Are events being received?\"\necho \"   - Any bounce\u002Fcomplaint events?\"\necho \"   - Last identify timestamp correct?\"\necho \"\"\necho \"3. Segments tab:\"\necho \"   - Which segments does user belong to?\"\necho \"   - Does segment match campaign audience?\"\necho \"\"\necho \"4. Campaigns > Find relevant campaign:\"\necho \"   - Is campaign status Active?\"\necho \"   - Does trigger event match?\"\necho \"   - Check 'Messages' tab for delivery attempts\"\n```\n\n### Step 3: Campaign Debugging\n\nCommon campaign issues and their investigation path:\n\n| Symptom | Check First | Then Check |\n|---------|------------|------------|\n| Campaign not triggering | Event name match (case-sensitive) | Campaign status (Active?) |\n| User not matched | Segment conditions | User attributes match segment? |\n| Email not delivered | User has `email` attribute | Bounce\u002Fsuppression status |\n| Liquid template broken | `message_data` has all required fields | Preview with real data in dashboard |\n| Wrong email content | Correct campaign version is Active | Template variables populated |\n| Delayed sends | Campaign \"Wait\" steps | Queue backlog in Customer.io |\n\n```typescript\n\u002F\u002F Programmatic campaign debug\nasync function debugCampaignTrigger(\n  userId: string,\n  eventName: string,\n  eventData: Record\u003Cstring, any>\n) {\n  const debug = new DebugCioClient();\n\n  console.log(\"=== Campaign Trigger Debug ===\\n\");\n\n  \u002F\u002F 1. Can we identify the user?\n  const identifyResult = await debug.debugIdentify(userId, {\n    _debug_campaign_check: true,\n  });\n\n  if (!identifyResult.success) {\n    console.log(\"\\nBLOCKER: Cannot identify user. Fix auth first.\");\n    return;\n  }\n\n  \u002F\u002F 2. Can we track the event?\n  const trackResult = await debug.debugTrack(userId, eventName, eventData);\n\n  if (!trackResult.success) {\n    console.log(\"\\nBLOCKER: Cannot track event. Check error above.\");\n    return;\n  }\n\n  console.log(\"\\n=== API Side OK ===\");\n  console.log(\"If campaign still not triggering, check in dashboard:\");\n  console.log(`1. Event name: \"${eventName}\" (must match exactly, case-sensitive)`);\n  console.log(\"2. Campaign status: must be Active (not Draft\u002FPaused)\");\n  console.log(\"3. Campaign audience: user must match segment\u002Ffilter\");\n  console.log(\"4. Campaign frequency: check if user already received\");\n  console.log(\"5. Suppression: check if user is suppressed\");\n}\n```\n\n### Step 4: Network Diagnostics\n\n```bash\n#!\u002Fusr\u002Fbin\u002Fenv bash\nset -euo pipefail\n# scripts\u002Fcio-network-diag.sh\n\necho \"=== Customer.io Network Diagnostics ===\"\necho \"\"\n\n# DNS resolution\necho \"--- DNS Resolution ---\"\nfor host in track.customer.io api.customer.io status.customer.io; do\n  IP=$(dig +short \"$host\" 2>\u002Fdev\u002Fnull | head -1)\n  echo \"${host}: ${IP:-FAILED}\"\ndone\n\necho \"\"\n\n# TLS check\necho \"--- TLS Certificate ---\"\necho | openssl s_client -connect track.customer.io:443 -servername track.customer.io 2>\u002Fdev\u002Fnull \\\n  | openssl x509 -noout -subject -issuer -dates 2>\u002Fdev\u002Fnull \\\n  || echo \"TLS check failed\"\n\necho \"\"\n\n# Latency test\necho \"--- Latency (5 samples) ---\"\nfor i in $(seq 1 5); do\n  LATENCY=$(curl -s -o \u002Fdev\u002Fnull -w \"%{time_total}\" \"https:\u002F\u002Ftrack.customer.io\")\n  echo \"Request ${i}: ${LATENCY}s\"\ndone\n\necho \"\"\n\n# Status page\necho \"--- Platform Status ---\"\ncurl -s \"https:\u002F\u002Fstatus.customer.io\u002Fapi\u002Fv2\u002Fstatus.json\" \\\n  | python3 -c \"import sys,json; d=json.load(sys.stdin); print(f'Status: {d[\\\"status\\\"][\\\"description\\\"]}')\" \\\n  2>\u002Fdev\u002Fnull || echo \"Could not fetch status\"\n```\n\n### Step 5: Incident Response Runbooks\n\n**P1 — Complete outage (all API calls failing):**\n1. Check https:\u002F\u002Fstatus.customer.io — is Customer.io down?\n2. If CIO is up: check your credentials (rotate if compromised)\n3. Enable circuit breaker to stop retries hitting a dead endpoint\n4. Switch to fallback queue (events stored in Redis\u002FKafka)\n5. Notify affected teams\n6. When restored: drain fallback queue, verify event delivery\n\n**P2 — High error rate (>5% failures):**\n1. Check error breakdown: which status codes?\n2. If 429: reduce concurrency, check rate limiter config\n3. If 5xx: check CIO status page, enable backoff\n4. If 401: credentials may have been rotated — check secrets manager\n5. Monitor error rate — escalate to P1 if not recovering\n\n**P3 — Delivery issues (messages not arriving):**\n1. Verify user has `email` attribute (People > user profile)\n2. Check suppression status (Suppressed badge)\n3. Check bounce history (Activity tab > filter bounces)\n4. Verify sending domain (Settings > Sending Domains)\n5. Check campaign is Active, trigger event matches\n6. Review spam folder and email headers\n\n**P4 — Webhook processing failures:**\n1. Verify webhook endpoint is publicly accessible\n2. Check signature verification (secret matches dashboard?)\n3. Review webhook event logs for parsing errors\n4. Check queue health if using async processing\n5. Verify Customer.io IP allowlist if using firewall\n\n## Diagnostic Commands\n\n```bash\n# Quick API health check\ncurl -s -u \"$CUSTOMERIO_SITE_ID:$CUSTOMERIO_TRACK_API_KEY\" \\\n  -X PUT \"https:\u002F\u002Ftrack.customer.io\u002Fapi\u002Fv1\u002Fcustomers\u002Fhealth-check\" \\\n  -H \"Content-Type: application\u002Fjson\" \\\n  -d '{\"_diag\":true}' \\\n  -w \"\\nHTTP: %{http_code} Time: %{time_total}s\\n\"\n\n# Check App API\ncurl -s -H \"Authorization: Bearer $CUSTOMERIO_APP_API_KEY\" \\\n  \"https:\u002F\u002Fapi.customer.io\u002Fv1\u002Fcampaigns\" \\\n  -w \"\\nHTTP: %{http_code}\\n\" | head -5\n\n# Platform status\ncurl -s \"https:\u002F\u002Fstatus.customer.io\u002Fapi\u002Fv2\u002Fstatus.json\" | python3 -m json.tool\n```\n\n## Error Handling\n\n| Issue | Solution |\n|-------|----------|\n| Intermittent 5xx | Transient — retry with backoff handles it |\n| Consistent 401 after deploy | Credentials changed — check env vars and secrets |\n| User receiving duplicate messages | Event deduplication or campaign frequency cap |\n| Webhook events stop arriving | Check endpoint health, CIO IP allowlist, SSL cert validity |\n\n## Resources\n\n- [Customer.io Status Page](https:\u002F\u002Fstatus.customer.io\u002F)\n- [Customer.io Community](https:\u002F\u002Fcommunity.customer.io\u002F)\n- [Reporting Webhooks Reference](https:\u002F\u002Fdocs.customer.io\u002Fintegrations\u002Fapi\u002Fwebhooks\u002F)\n- [Troubleshooting Deliverability](https:\u002F\u002Fdocs.customer.io\u002Fjourneys\u002Fdeliverability\u002F)\n\n## Next Steps\n\nAfter troubleshooting, proceed to `customerio-reliability-patterns` for fault tolerance.\n",{"name":5,"tags":24,"author":29,"license":15,"version":30,"description":31,"allowed-tools":32,"compatible-with":33},[25,26,27,28],"saas","customer-io","debugging","incident-response","Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Apply Customer.io advanced debugging and incident response.\nUse when diagnosing complex delivery issues, investigating\ncampaign failures, or running incident playbooks.\nTrigger: \"debug customer.io\", \"customer.io investigation\",\n\"customer.io troubleshoot\", \"customer.io incident\", \"customer.io not delivering\".\n","Read, Write, Edit, Bash(curl:*), Bash(npx:*), Glob, Grep","claude-code, codex, openclaw","main","99825ad3f3bcc6597ddcc7294a14e6e922f2b67b","skills\u002Fsaas-packs--customerio-pack--customerio-advanced-troubleshooting",0,"https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills","https:\u002F\u002Fgithub.com\u002Fjukeyman","https:\u002F\u002FRJBUSINESSSOLUTIONS.ORG","Credit and Finance Expert | Developer\r\n\r\nI'm Rick Jefferson, a seasoned credit and finance expert with over a decade of experience in financial literacy,","2026-07-13 07:03:29",{"source":8,"skillName":5,"commands":44,"prompt":54,"zipAvailable":55},[45,48,51],{"tool":46,"command":47},"npx","npx skills add jukeyman\u002Fjukeyman-skills --skill customerio-advanced-troubleshooting",{"tool":49,"command":50},"bunx","bunx skills add jukeyman\u002Fjukeyman-skills --skill customerio-advanced-troubleshooting",{"tool":52,"command":53},"pnpm","pnpm dlx skills add jukeyman\u002Fjukeyman-skills --skill customerio-advanced-troubleshooting","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fsaas-packs--customerio-pack--customerio-advanced-troubleshooting\u002FSKILL.md",true,[],[58,65,72,79,86,94],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M79ANS2SM329NEP5ZCX106RR","zustand-store-creator","Create zustand store creator operations. Auto-activating skill for Frontend Development.\nTriggers on: zustand store creator, zustand store creator\nPart of the Frontend Development skill category. Use when working with zustand store creator functionality. Trigger with phrases like \"zustand store creator\", \"zustand creator\", \"zustand\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzustand-store-creator\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M79AMZKP4YDEZ7EHG1Y7PP74","zero-trust-config-helper","Configure with zero trust config helper operations. Auto-activating skill for Security Advanced.\nTriggers on: zero trust config helper, zero trust config helper\nPart of the Security Advanced skill category. Use when configuring systems or services. Trigger with phrases like \"zero trust config helper\", \"zero helper\", \"zero\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzero-trust-config-helper\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M79AMJSBCEJQNBTYNAHYN5HM","zapier-integration-helper","Assist with zapier integration helper operations. Auto-activating skill for Business Automation.\nTriggers on: zapier integration helper, zapier integration helper\nPart of the Business Automation skill category. Use when working with APIs or building integrations. Trigger with phrases like \"zapier integration helper\", \"zapier helper\", \"zapier\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzapier-integration-helper\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M79AHJZGVMARS13VFQYRR1MP","yaml-config-validator","Validate yaml config validator operations. Auto-activating skill for DevOps Basics.\nTriggers on: yaml config validator, yaml config validator\nPart of the DevOps Basics skill category. Use when configuring systems or services. Trigger with phrases like \"yaml config validator\", \"yaml validator\", \"yaml\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fyaml-config-validator\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":90,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":19},"01M79AHGDZRN0020RDQSQDPAM8","xvary-stock-research","Thesis-driven equity analysis from public SEC EDGAR and market data; \u002Fanalyze, \u002Fscore, \u002Fcompare workflows with bundled Python tools (Claude Code, Cursor, Codex).","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxvary-stock-research\u002FSKILL.md",[],[],{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"publishedAt":19},"01M79AHCYJ9FV9RMHQ24HDRN33","xss-vulnerability-scanner","Scan xss vulnerability scanner operations. Auto-activating skill for Security Fundamentals.\nTriggers on: xss vulnerability scanner, xss vulnerability scanner\nPart of the Security Fundamentals skill category. Use when working with xss vulnerability scanner functionality. Trigger with phrases like \"xss vulnerability scanner\", \"xss scanner\", \"xss\".","https:\u002F\u002Fgithub.com\u002Fjukeyman\u002Fjukeyman-skills\u002Fblob\u002Fmain\u002Fskills\u002Fxss-vulnerability-scanner\u002FSKILL.md",[],[]]