-
Notifications
You must be signed in to change notification settings - Fork 41
Update troubleshooting.md #1633
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Formatting suggestions
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Overall readability score: 58.04 (🟢 +0)
View detailed metrics🟢 - Shows an increase in readability
Averages:
View metric targets
|
| - "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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
📝 [vale] reported by reviewdog 🐶
[Google.Passive] In general, use active voice instead of passive voice ('were exhausted').
| - "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. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
📝 [vale] reported by reviewdog 🐶
[Google.Passive] In general, use active voice instead of passive voice ('been sent').
| 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 multiple 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, we will send all messages at once, applying some delay between messages. This is to prevent overloading the webhook consumer endpoint. If your system has rate limiting in place, consider this scenario to avoid further failures. See details of [webhook endpoint rate limiting](/using-the-api/webhooks/create-consumer#endpoint-rate-limits). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
📝 [vale] reported by reviewdog 🐶
[Google.Will] Avoid using 'will'.
|
Link check results for preview deployment (https://codat-docs-git-pj-simpson-bold-list-codat.vercel.app): |
Updating to make some bullet points bold, as per @dcoplowe 's suggestion.
Note
Docs update (webhooks troubleshooting)
Message Statusas bolded bullet points for clarityMultiple messagesrecovery guidance to state messages are sent at once with delays between them; adds link toendpoint rate limitsand removes support-escalation noteWritten by Cursor Bugbot for commit 3c34c1e. This will update automatically on new commits. Configure here.