diagnostico-evolution-api

Diagnose Evolution API production failures in containers, webhooks, instances, and WhatsApp message flow.

5|Updated Jun 3, 2026
One-click install
npx skills add https://github.com/rafael-fae/agent-ops-worflow --skill diagnostico-evolution-api
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: diagnostico-evolution-api
Source: https://github.com/rafael-fae/agent-ops-worflow/tree/main/archive/skills/operacao/diagnostico-evolution-api
Command: npx skills add https://github.com/rafael-fae/agent-ops-worflow --skill diagnostico-evolution-api

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps troubleshoot production issues in Evolution API deployments, especially when WhatsApp instances, webhooks, authentication, or the manager UI stop behaving as expected.

Core Features & Use Cases

  • Container and service checks: Verify whether the Evolution API container, PostgreSQL, Redis, and webhook services are running correctly.
  • Webhook and instance debugging: Diagnose missing messages, broken event formats, instance persistence problems, and manager UI mismatches.
  • Upgrade and migration recovery: Handle license reactivation, server migration, version-specific bugs, rollback decisions, and WhatsApp Business integration failures.
  • Use case: A production WhatsApp bot stops receiving messages after an upgrade; this Skill guides you through checking the API key, webhook payload format, instance records, and rollback options.

Quick Start

Use this skill to diagnose the current Evolution API incident, identify the failing component, and recommend the safest fix or rollback path.

Frequently Asked Questions about diagnostico-evolution-api

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

FAQPage Schema
Why does my Evolution API container stop receiving WhatsApp messages after an upgrade?

Evolution API upgrade regressions often break WhatsApp message flow due to changed webhook payload formats or corrupted instance records. Diagnosing the incident involves validating API keys, checking instance persistence in PostgreSQL, and verifying event formats to identify the failing component.

How do I debug missing webhooks in my Evolution API deployment?

To debug missing Evolution API webhooks, verify the webhook service is running correctly alongside Redis and PostgreSQL. You must validate API keys, inspect event payload formats, and check instance records to ensure webhook routing is properly configured and messages are not being dropped.

What is the best way to fix Evolution API manager UI mismatches and instance persistence loss?

Fixing Evolution API manager UI mismatches and persistence loss requires checking database state in PostgreSQL and verifying instance records. Diagnose the production failure by validating API keys and ensuring the container services are running correctly to restore instance synchronization.

How do I recover WhatsApp Business integration and licensing failures during Evolution API server migration?

Recovering WhatsApp Business integration and licensing failures during Evolution API server migration involves validating API keys and checking database state. The safest recovery path includes evaluating rollback decisions, reactivating licenses, and verifying deployment-specific instance records.

Does Evolution API diagnostics support troubleshooting systemd and Docker service failures?

Evolution API diagnostics supports troubleshooting systemd and Docker service failures by verifying whether the Evolution API container, PostgreSQL, Redis, and webhook services are running correctly. It applies to server-side debugging scenarios to identify failing components and recommend fixes.

What should I do when Evolution API webhook events are not routing to my WhatsApp bot correctly?

When Evolution API webhook events are not routing to your WhatsApp bot correctly, validate the API key and inspect the webhook payload format. Diagnose the routing failure by checking webhook service status, event formats, and database state to recommend the safest fix.