Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Mensagem ficam como LIDA

Open
#2,661 1 comment 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
38/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Quiet
Tech stack
docker, typescript
Domain
api, backend

Research direction

Start by reproducing the behavior with Evolution API version 2.2.3 in the reported Docker environment, using the same WhatsApp and N8n message flow. No source file or test is named, so trace the message-receipt and read-status handling while collecting logs. Done means incoming messages arrive without being marked as read or losing their unread indication.

Written by the indexing model from the issue text.

Description

bug
Welcome!
  • Yes, I have searched for similar issues on GitHub and found none.
What did you do?

Tenho uma unica instancia conectado com o meu whatsapp mesmo, não estou fazendo spam, estou usando para envio de mensagens do meu N8n, so que , depois de instalado e sincronizado com o EvolutionApi, meu whats Recebe mensagem , ao entar no whasts , já esta como "Lida" a mensagem,

What did you expect?

que não desse como LIDAS as minhas mensagen no meu WatsApp que eu já tenho !

What did you observe instead of what you expected?

que minhas mensagen no meu whasts chegam, e não fica "mostando" que chegou mensagem!

Screenshots/Videos

No response

Which version of the API are you using?

evolution_exchange
Version: 2.2.3

What is your environment?

Docker

Other environment specifications

Contaboo VPS Linux

If applicable, paste the log output

No response

Additional Notes

No response

Dominant language
TypeScript
Stars
9.6k
Forks
7.3k
PR merge metrics
No merged PRs in 30d

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from evolution-foundation/evolution-api

All issues in evolution-foundation/evolution-api

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.