From eeea4fd818572f19ad18a74f617123c3a9d0af53 Mon Sep 17 00:00:00 2001 From: Peter Simpson <40800258+pj-simpson@users.noreply.github.com> Date: Tue, 15 Jul 2025 10:38:37 +0100 Subject: [PATCH 1/2] Update troubleshooting.md Formatting suggestions --- docs/using-the-api/webhooks/troubleshooting.md | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/using-the-api/webhooks/troubleshooting.md b/docs/using-the-api/webhooks/troubleshooting.md index f58e24cff..29b070340 100644 --- a/docs/using-the-api/webhooks/troubleshooting.md +++ b/docs/using-the-api/webhooks/troubleshooting.md @@ -29,10 +29,10 @@ A webhook consumer endpoint which is disabled after the 5 min retry, but then re ## Message Status -- "Success" indicates that there was at least one attempt for that message that succeeded against it's endpoint. -- "Failure" indicates that all attempts were exhausted, and none of them succeeded. -- "Attempting" indicates that at least one attempt has been sent and there are further attempts scheduled as part of the retry policy. -- "Sending" indicates that the process of sending the webhook has begun but there have been no delivery attempts yet. +- **Success** indicates that there was at least one attempt for that message that succeeded against it's endpoint. +- **Failure** indicates that all attempts were exhausted, and none of them succeeded. +- **Attempting** indicates that at least one attempt has been sent and there are further attempts scheduled as part of the retry policy. +- **Sending** indicates that the process of sending the webhook has begun but there have been no delivery attempts yet. ## Recover failed and missed messages From 219304205fd1c473fd34a778686eef6c70a80ebf Mon Sep 17 00:00:00 2001 From: Peter Simpson <40800258+pj-simpson@users.noreply.github.com> Date: Tue, 15 Jul 2025 10:47:08 +0100 Subject: [PATCH 2/2] Update troubleshooting.md --- docs/using-the-api/webhooks/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/using-the-api/webhooks/troubleshooting.md b/docs/using-the-api/webhooks/troubleshooting.md index 29b070340..50f7507d3 100644 --- a/docs/using-the-api/webhooks/troubleshooting.md +++ b/docs/using-the-api/webhooks/troubleshooting.md @@ -67,7 +67,7 @@ Then, click the triple-dot menu on the right and choose one of the applicable op For more granular date control, you can scroll to the endpoint's message attempts, click the triple-dot options menu of a specific message, and choose **Replay > Replay all failed messages since this time**. -During the recovery of mutiple messages, all messages will be sent at once with some jitter applied in order to prevent overloading the webhook consumer endpoint. If your system has rate-limiting in place, the number of messages to recover may be an important consideration to avoid further failures. Please reach out to Codat Support if unsure. +During the recovery of mutiple messages, all messages will be sent at once with some jitter applied in order to prevent overloading the webhook consumer endpoint. If your system has rate-limiting in place, the number of messages to recover may be an important consideration to avoid further failures. [Please see our docs around rate limiting endpoints](/using-the-api/webhooks/create-consumer). ### Idempotency