[Feature] MESSAGES_UPDATE webhook não inclui errors da Meta (Business API)
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 78/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Quiet
- Tech stack
- typescript
- Domain
- api
Research direction
Start in whatsapp.business.service.ts around line 980, where the MESSAGES_UPDATE webhook message is assembled. Trace the failed Meta status handling and verify that the webhook payload preserves item.errors, using null when no errors are present. Done means MESSAGES_UPDATE includes the error array for failed Business API messages without changing the existing fields.
Written by the indexing model from the issue text.
Description
Welcome!
- Yes, I have searched for similar requests on GitHub and found none.
What type of feature?
Functionality
What is the motivation for the request?
Problema
No whatsapp.business.service.ts, quando a Meta retorna status failed com detalhes do erro, o webhook MESSAGES_UPDATE descarta o array errors.
Código atual (~linha 980):
const message: any = {
messageId: findMessage.id,
keyId: key.id,
remoteJid: key.remoteJid,
fromMe: key.fromMe,
participant: key?.remoteJid,
status: item.status.toUpperCase(),
instanceId: this.instanceId,
};
this.sendDataWebhook(Events.MESSAGES_UPDATE, message);
### Usage Examples
## Solução
status: item.status.toUpperCase(),
errors: item.errors || null, // ← adicionar
instanceId: this.instanceId,
### How should the feature be developed?
_No response_
### Additional Notes
_No response_- Dominant language
- TypeScript
- Stars
- 9.6k
- Forks
- 7.3k
- PR merge metrics
- No merged PRs in 30d
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from evolution-foundation/evolution-api
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
evolution-foundation/evolution-api#2700 · 1 comment ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
All issues in evolution-foundation/evolution-api
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
receptron/mulmoterminal#2264 ·
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
components-web-app/docs#96 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
simonsobs/tileviewer#114 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100