Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

[BUG] chats.update / initial history sync discard the archived flag before it reaches webhooks or the database

Aberta
  • Algo errado?
#2,743 1 comentário 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 5 dias

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
67/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
postgresql, typescript
Domínio
api, backend, databases

Direção de pesquisa

Start in whatsapp.baileys.service.ts and compare the chats.update and messaging-history.set handlers with the compiled path cited in the issue. Then inspect the Prisma Chat model and the findChats flow. Done means archived state reaches webhook payloads, persists on Chat rows, and is returned by findChats, with the relevant migration and tests or reproduction checks passing.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

📋 Bug Description

When a chat is archived/unarchived on the phone (or any linked device), Baileys emits the change via chats.update with an archived: true/false field. Evolution's chats.update handler in whatsapp.baileys.service.ts (WHATSAPP-BAILEYS integration) discards every field except remoteJid before forwarding to the webhook or writing to the DB:

"chats.update": async (e) => {
  const chatsRaw = e.map(chat => ({ remoteJid: chat.id, instanceId: this.instanceId }));
  this.sendDataWebhook('chats.update', chatsRaw);
  for (const chat of e)
    await this.prismaRepository.chat.updateMany({
      where: { instanceId: this.instanceId, remoteJid: chat.id, name: chat.name },
      data: { remoteJid: chat.id },
    });
}

(from compiled dist/api/integrations/channel/whatsapp/whatsapp.baileys.service.js, v2.3.7)

The messaging-history.set handler (emits chats.set) does the same trim, and additionally only forwards chats not already in the Chat table — so even a fresh reconnect can't backfill archive state for chats Evolution already knows about.

The Chat Postgres table also has no archived column at all:

Table "public.Chat"
id | remoteJid | labels | createdAt | updatedAt | instanceId | name | unreadMessages

So there is currently no way for an integrator to learn a chat's real archived state via webhook, DB, or GET /chat/findChats/:instance — it's dropped at the earliest point in Evolution's own pipeline.

🔄 Steps to Reproduce

  1. Connect an instance (WHATSAPP-BAILEYS) with the chats.update webhook enabled.
  2. Archive (or unarchive) any chat directly on the linked phone.
  3. Inspect the delivered chats.update webhook payload.
  4. Check the Chat row for that remoteJid via GET /chat/findChats/:instance or Postgres directly.

✅ Expected Behavior

chats.update carries the chat's current archived boolean, it's persisted on the Chat row, and findChats returns it — so integrators can mirror the phone's real archived list instead of maintaining a local-only flag.

❌ Actual Behavior

chats.update/chats.set payloads only ever contain {remoteJid, instanceId[, name]}. archived is silently discarded.

🌍 Environment

  • OS: Ubuntu (Docker host)
  • Evolution API version: 2.3.7
  • Integration: WHATSAPP-BAILEYS
  • Database: PostgreSQL 13

📝 Additional Context / Proposed Fix

Sketch of a fix, for whoever picks this up:

  1. Add archived Boolean @default(false) to the Chat Prisma model (migration).
  2. In chats.update, forward archived: chat.archived in the webhook payload and include it in the chat.updateMany write.
  3. In messaging-history.set, same field addition; consider also letting already-known chats' archived/pinned/muteEndTime refresh on reconnect, since today only brand-new chats get forwarded at all.
  4. Confirm findChats selects/returns the new column once it exists.

Related: #2495 looks like a different symptom in the same area (write-side archiveChat endpoint erroring) — this is the read side: archive state never reaching the integrator in the first place.

Linguagem predominante
TypeScript
Estrelas
9.9k
Forks
7.4k
Nenhum PR com merge em 30d

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de evolution-foundation/evolution-api

Todas as issues de evolution-foundation/evolution-api

Issues semelhantes

Mais issues de TypeScript

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.