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!)

[devlikepro]

@Ysnkr
WAHA retries requests when:

• The response is not a 2xx success code (e.g., 4xx or 5xx),
• Or there are other failures such as:
  • Network errors
  • Webhook Receiver crashes that prevent any response from being sent (like @TitoBahe mentioned about no status back)

[EverStarck]

Hi @devlikepro I'm having the issue of duplicated messages. Different x-webhook-request-id but same id. I'm using NOWEB version 2025.4.1
Happens on every message.

Logs show that it configured the webhook twice:

2025-04-25T18:27:11.500122651Z [18:27:11.306] INFO (SessionManager/1): session:default - Starting session... {"reqId":15,"session":"default"}
2025-04-25T18:27:11.501003959Z [18:27:11.310] INFO (WebhookConductor/1): session:default - Configuring webhooks for https://site.com/webhook... {"reqId":15,"session":"default"}
2025-04-25T18:27:11.501021592Z [18:27:11.311] INFO (WebhookConductor/1): session:default - Webhooks were configured for https://site.com/webhook. {"reqId":15,"session":"default"}
2025-04-25T18:27:11.501027072Z [18:27:11.311] INFO (WebhookConductor/1): session:default - Configuring webhooks for https://site.com/webhook... {"reqId":15,"session":"default"}
2025-04-25T18:27:11.501031430Z [18:27:11.311] INFO (WebhookConductor/1): session:default - Webhooks were configured for https://site.com/webhook. {"reqId":15,"session":"default"}
2025-04-25T18:27:11.501062407Z [18:27:11.373] INFO (1): session:default - Session has been started. {"reqId":15,"session":"default"}

full logs here (pls let me know if there's some sensitive data so I can delete it)

What other info you need and how can I get it so you can debug more easily?
Thanks!

[EverStarck]

update, found the issue: I was passing the webhook in the .env, but the dashboard didn't show it on the session config, so I added it again bruh.

maybe this could be a good UI/UX update to the dashboard:)

[devlikepro]

@EverStarck good idea!
like "non editable webhook configuration" for each session, so you know global settings as well

[devlikepro]

Created a feature request for that!
#929