skills.rest
adaptive-enforcement-lab
adaptive-enforcement-labOFFICIAL
Explore all skills by this author →
GitHub

troubleshooting

Diagnose and fix failures in Argo Events event-driven workflows.

3|3|Updated Jan 4, 2026
Search Tags:#debugging#troubleshooting#diagnostics#event-driven#workflows#argo-events
One-click install
npx skills add https://github.com/adaptive-enforcement-lab/claude-skills --skill troubleshooting-adaptive-enforcement-lab
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: troubleshooting
Source: https://github.com/adaptive-enforcement-lab/claude-skills/tree/main/plugins/patterns/skills/troubleshooting
Command: npx skills add https://github.com/adaptive-enforcement-lab/claude-skills --skill troubleshooting-adaptive-enforcement-lab

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Troubleshooting event-driven workflows can be opaque when failures occur across multiple components. This guide provides a systematic approach to identify, diagnose, and fix issues in real-time production systems.

Core Features & Use Cases

  • Systematic debugging flow: guides you from EventSource to Workflow using clear sequence diagrams.
  • Practical diagnostics: includes quick commands and checks for EventSource, EventBus, Sensor, and Workflow health.
  • Education and troubleshooting: links to related guides and common patterns to accelerate resolution.

Quick Start

Begin by running the Quick Diagnostic Commands to identify where events stall and then apply the recommended debugging steps.

Frequently Asked Questions about troubleshooting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I troubleshoot event-driven workflows when events stop triggering?▼

To troubleshoot event-driven workflows, run quick diagnostic commands to identify where events stall, then apply a systematic debugging flow checking EventSource, EventBus, Sensor, and Workflow components.

What is the best way to debug Argo Events pipelines across multiple components?▼

The best way to debug Argo Events pipelines is following a systematic sequence from EventSource to Workflow, applying specific diagnostic commands and logging checks across EventBus, Sensor, and Trigger components.

Why does my Sensor fail to trigger Argo Events workflows in production?▼

Your Sensor may fail to trigger Argo Events workflows due to EventBus connectivity issues or EventSource failures; use diagnostic commands to check component health and identify where events stall.

What diagnostic commands should I run to check EventSource and EventBus health?▼

Run the quick diagnostic commands specified in the troubleshooting guide to check EventSource and EventBus health, identify event stalls, and apply recommended debugging steps across the pipeline.

Related Skills

Explore More Software Engineering Skills→
adaptive-enforcement-labadaptive-enforcement-lab
3

argo-events-setup-guide

Configure and deploy Argo Events EventSource, EventBus, and Sensor components on Kubernetes clusters.

Official
Intermediate
adaptive-enforcement-labadaptive-enforcement-lab
3

reliability-patterns

Configure Argo Events retry and dead-letter patterns for durable event delivery.

Official
Intermediate
adaptive-enforcement-labadaptive-enforcement-lab
3

argo-events

Connect external event sources to trigger Argo Workflows in Kubernetes.

Official
Advanced
googlegoogle
68

dev-debugging

Diagnose and fix Capsem bugs through a test-driven three-step debugging workflow.

Official
Advanced