upgrade-evolution-api

Guide Evolution API upgrades and recover from failed migrations and webhook issues.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill guides operators through a high-risk Evolution API upgrade, preventing downtime, broken migrations, orphaned foreign keys, license loss, and webhook failures during version changes.

Core Features & Use Cases

  • Clean upgrade planning: Updates the container image path from v2.3.7 to 2.4.0+ and explains the correct upgrade sequence.
  • Failure recovery: Handles database resets, orphan cleanup, rollback options, and verification steps when Prisma migrations fail.
  • Production-specific troubleshooting: Covers Redis-only instances, nginx DNS cache issues, license reactivation, and webhook routing for both host-based and Meta Cloud API flows.
  • Use case: An ops engineer upgrades Evolution API, discovers foreign key errors, and uses this Skill to restore service, revalidate the instance, and confirm webhook delivery.

Quick Start

Use this skill to assess your current Evolution API version, follow the safest upgrade path, and verify that the database, license, nginx, and webhook configuration all work after the change.

Frequently Asked Questions about upgrade-evolution-api

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

FAQPage Schema
How do I recover from a failed Prisma migration when upgrading Evolution API?

Recovering from a failed Evolution API migration requires coordinated database verification, orphaned foreign key cleanup, and Prisma database resets to resolve container restart issues and restore service safely.

Why does Evolution API lose its license and webhook routing after a version upgrade?

Evolution API license and webhook routing failures occur after version changes due to configuration resets. Operators must perform license reactivation and validate webhook endpoints for both host-based and Meta Cloud API flows to restore connectivity.

How do I safely upgrade Evolution API from v2.3.7 to 2.4.0+ in production?

Safely upgrading Evolution API involves updating the container image path from v2.3.7 to 2.4.0+ and following a strict upgrade sequence, requiring PostgreSQL, Redis, and nginx verification alongside webhook validation after the change.

Does upgrading Evolution API require DNS cache troubleshooting for nginx?

Yes, upgrading Evolution API requires nginx DNS cache troubleshooting in production deployments to ensure stable webhook integrations and correct routing for WhatsApp Business or Baileys-based instances after applying version changes.

How do I fix foreign key violations in PostgreSQL after an Evolution API update?

Fixing foreign key violations in PostgreSQL after an Evolution API update requires orphan cleanup and database verification to successfully reactivate WhatsApp Business or Baileys-based instances and prevent container restart loops.

What is the correct upgrade sequence for Evolution API with PostgreSQL and Redis?

The correct Evolution API upgrade sequence involves updating the container image, verifying PostgreSQL, troubleshooting Redis and nginx DNS cache, and validating webhook endpoints to prevent downtime and license loss.