Skip to content

Commit d2b1768

Browse files
committed
Clarify webhook retries/potential duplicates
1 parent d777260 commit d2b1768

1 file changed

Lines changed: 2 additions & 7 deletions

File tree

source/includes/webhooks.md

Lines changed: 2 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -10,11 +10,6 @@ only one specific project.
1010
All activities for the project(s) configured for the webhook are sent to the
1111
endpoint. You can decide if you want to act on the activity or ignore it.
1212

13-
## Webhooks Availabilty
14-
15-
If you have access to the API, you also have access to webhooks. For more
16-
information, see [the Availablity section above](/#availablity).
17-
1813
## Webhooks Setup
1914

2015
You can add a webhook endpoint in the **Integrations** section of your charity
@@ -136,9 +131,9 @@ Your endpoint should respond within 30 seconds with an HTTP 200 response.
136131

137132
If we receive any other response code, or we do not receive a response within 30
138133
seconds, the system will retry sending the notification indefinently until we
139-
receive an HTTP 200 response.
134+
receive an HTTP 200 response within 30 seconds.
140135

141-
The system retrys at exponentially-increasing intervals equal to
136+
The system retries at exponentially-increasing intervals equal to
142137
(failure_count^4 + 3) seconds. This means that delivery will be retried 4
143138
seconds after the first failure, 19 seconds after the second, 84 seconds after
144139
the third, 259 seconds after the fourth, and so on until it succeeds.

0 commit comments

Comments
 (0)