Diálogo 360 - Templates API Partial Service Disruption – Detalhes do incidente

Experimentando Desempenho Parcialmente Degradado

Templates API Partial Service Disruption

Resolvido
Operacional
Começou em há cerca de 9 horasDurado menos de um minuto

Afetado

360dialog Infrastructure

Operacional undefined 9:25 AM para 9:25 AM

API de negócios do WhatsApp 360dialog

Operacional undefined 9:25 AM para 9:25 AM

API do parceiro

Operacional undefined 9:25 AM para 9:25 AM

Atualizações
  • Resolvido
    Resolvido

    Root Cause Analysis – Templates API Partial Service Disruption
    Date: 09 March 2026
    Duration: ~1 hour
    Affected Service: Templates API (Partners API)

    Summary


    On 09 March 2026, a configuration inconsistency introduced during a routine production release caused a partial disruption of the Templates API. As a result, some template-related API requests were not processed correctly for approximately one hour.
    The issue was identified through internal monitoring alerts and resolved shortly after detection.

    Timeline (UTC)


    07:20 – Production release deployed.
    08:20 – Internal monitoring alert triggered indicating abnormal behavior.
    08:20 – Investigation started.
    08:34 – Root cause identified and configuration corrected. Fix deployed.
    08:38 – Service confirmed fully operational.

    Root Cause


    During a scheduled production release, one configuration component was not updated consistently with the rest of the deployment. This resulted in a mismatch that temporarily affected the Templates API routing.

    Resolution


    The configuration was updated to align with the production deployment settings. Once the correction was applied, the Templates API immediately resumed normal operation.

    Preventive Measures


    To reduce the risk of similar issues in the future, we are implementing the following improvements:

    • Reviewing configuration management to reduce duplicated configuration elements.

    • Adding additional validation checks during deployments.

    • Improving deployment procedures to ensure configuration consistency across all components.

    We apologize for any inconvenience this incident may have caused and appreciate your understanding.