From b079cc12f43459c5908d34a2f9781cd0562e4efe Mon Sep 17 00:00:00 2001 From: Brian Candler Date: Sun, 7 Mar 2021 17:25:49 +0000 Subject: [PATCH] Doc: give correct navigation to the "Django RQ" section --- docs/additional-features/webhooks.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/additional-features/webhooks.md b/docs/additional-features/webhooks.md index 845a6745d..d6fa27f51 100644 --- a/docs/additional-features/webhooks.md +++ b/docs/additional-features/webhooks.md @@ -68,7 +68,7 @@ If no body template is specified, the request body will be populated with a JSON ## Webhook Processing -When a change is detected, any resulting webhooks are placed into a Redis queue for processing. This allows the user's request to complete without needing to wait for the outgoing webhook(s) to be processed. The webhooks are then extracted from the queue by the `rqworker` process and HTTP requests are sent to their respective destinations. The current webhook queue and any failed webhooks can be inspected in the admin UI under Django RQ > Queues. +When a change is detected, any resulting webhooks are placed into a Redis queue for processing. This allows the user's request to complete without needing to wait for the outgoing webhook(s) to be processed. The webhooks are then extracted from the queue by the `rqworker` process and HTTP requests are sent to their respective destinations. The current webhook queue and any failed webhooks can be inspected in the admin UI under System > Background Tasks. A request is considered successful if the response has a 2XX status code; otherwise, the request is marked as having failed. Failed requests may be retried manually via the admin UI.