Queue penalty
To ensure the stability of our webhook system and provide predictability regarding delivery attempts, Asaas uses a penalty system. When your endpoint starts returning consecutive errors, we apply increasing time intervals between retry attempts.
This mechanism applies to both sequential and non-sequential webhook configurations
Important
For sequential mode configurations, the order in which events are delivered is strictly guaranteed. Therefore, if an event is penalized, all subsequent events in the same queue will wait for its successful delivery before being processed.
How does the penalty work?
If your application returns any response that is not in the 200
family, we consider it a failure. After the first failure, Asaas will begin the following cycle of retries and notifications:
Attempt | Time | Notification action |
---|---|---|
1 | 0 | |
2 | 30 segundos | |
3 | 1 min | |
4 | 3,5 min | |
5 | 5 min | 1st Alert Email |
6 | 15 min | |
7 | 25 min | |
8 | 1 hr | |
9 | 1 hr | |
10 | 1 hr | 2nd Alert Email |
11 | 1 hr | |
12 | 1 hr | |
13 | 1 hr | |
14 | 1 hr | |
15 | 3 hrs | 3rd Email (Queue Paused) |
After 15 consecutive failures, the delivery queue for that specific webhook configuration is Paused.
New events will continue to be generated and queued, but they will not be sent until you manually reactivate the queue. See more details about the paused queue at webhooks with queue paused.
Updated about 4 hours ago