From c7300dfbcf8987322aedec0626cf913a82ddc08e Mon Sep 17 00:00:00 2001 From: Rodribm10 Date: Fri, 1 May 2026 21:29:07 -0300 Subject: [PATCH] fix(captain/hermes): nao enviar typing_off explicito Antes: typing_on -> sleep delay -> create msg DB -> typing_off -> SendReplyJob envia via wuzapi -> msg chega no celular (2-5s depois). Resultado visual quebrado: cliente ve "digitando..." sumir antes da msg chegar, gap visivel. Agora: typing_on -> sleep -> create msg -> deixa rolar. WhatsApp do cliente cancela typing automaticamente quando msg eh entregue. Sequencia fica natural. Co-Authored-By: Claude Opus 4.7 (1M context) --- enterprise/app/jobs/captain/hermes/delayed_reply_job.rb | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/enterprise/app/jobs/captain/hermes/delayed_reply_job.rb b/enterprise/app/jobs/captain/hermes/delayed_reply_job.rb index e460b858b..fc32d8191 100644 --- a/enterprise/app/jobs/captain/hermes/delayed_reply_job.rb +++ b/enterprise/app/jobs/captain/hermes/delayed_reply_job.rb @@ -39,9 +39,10 @@ class Captain::Hermes::DelayedReplyJob < ApplicationJob create_outgoing_message(conversation, content) - # WhatsApp cliente costuma sumir typing automático ao receber msg, mas - # mandamos typing_off explícito por segurança. - send_typing(conversation, 'typing_off') if delay.positive? + # NÃO mandamos typing_off explícito — WhatsApp cancela o indicador + # automaticamente quando a msg chega no celular. Mandar paused agora + # quebraria visualmente: typing some -> gap de 2-5s ate msg ser + # entregue via SendReplyJob -> msg chega. Deixa o WhatsApp gerenciar. end private