Retries Policy

[TitoBahe]

Does somebody know if I set the retries.delaySeconds to 2 seconds, it waits 2 seconds to recive a response from my api, if it doesnt receive any response, it sends another req to it? because sometimes I am receiving the same message repeatedly but never more than the amount I set in retries.attempts.
As I am getting no errors, I suspect thats hwo it works.

[devlikepro]

No, delay seconds is for "delay between retries", not the timeout.
https://waha.devlike.pro/docs/how-to/webhooks/

If you set it to 2 and apply policy it gives you this:

• constant - retry with the same delay between attempts (2, 2, 2, 2)
• linear - retry with linear backoff (2, 4, 6, 8)
• exponential - retry with exponential backoff with 20% jitter (2, 4.1, 8.4, 16.3).

I don't think there's any timeout in webhooks at all 🤔

Could you check the following for the duplicated events

1. Check X-Webhook-Id http header
2. Check message.id

based on that we could understand what exactly happens.

• If payload has the same X-Webhook-Id - it means that it's retries, likely there's some logs about why it retried the call
• If payload has different header, but the same message.id - it means that WAHA sends duplicated message. IT could happen time to time due to missed ack to server, but should be rare case (we'd love to make it 0 with your help!)

[TitoBahe]

So, I changed the retries.delaySeconds from 2 secs to 120 secs and dupplicated msgs stopped appearing. I think they are timeouts.

what would I lose if instead of setting a retry policy, I just return status 500 instead, not even listing retries on the creation of a session?
I know WAHA has a dead letter queue built-in.

So, the retries attribute, when creating a session, just reconfigure the default one, therefore, I wont be creating anymore timeouts when I receive a new msg or the retries I set when I create a new session just add another timeout to be executed?

I am asking those questions because I want to save as much resources as possible and dont want one more timeout to be set everytime I receive a msg.

[devlikepro]

Intetersting, but it doesn't look like timeout on WAHA side.
I've set webhook url to https://httpbin.org/delay/10 (aka 10 seconds delay) with
retries.delaySeconds=2, policy=constant
and it sends exactly 1 request.

Could it be 2 sec timeout on your webhook handler?
Weird tho, there's no errors in the logs your provided in the first request 🤔

It could be some internal timeout where we don't send ack in proper time and server re-sends us the message (or it's retry internal one)

[devlikepro]

wait, is event type the same in it, both message? Or one with message and the seconds one with message.any?
Could you share the full payload (except private data) for both webhooks?

If you listen both message and message.any it WILL send for YOUR messages 2 webhooks with the same message.id because it's a different messages.

[devlikepro]

Basiclly

• message event - when you receive a message from others
• message.any - when you receive a message from others + your own messages (either via API or phone)

[TitoBahe]

wait, is event type the same in it, both message? Or one with message and the seconds one with message.any? Could you share the full payload (except private data) for both webhooks?

If you listen both message and message.any it WILL send for YOUR messages 2 webhooks with the same message.id because it's a different messages.

Yes, they are both message.any. I dont use message event, only message.any.

And I am sorry, I dont think I have the full payload anymore. I did so many things on the project already. I lost them... my bad..
I will send the logs here If I get any other.