Skip to content

Conversation

@pj-simpson
Copy link
Collaborator

@pj-simpson pj-simpson commented Jul 15, 2025

Updating to make some bullet points bold, as per @dcoplowe 's suggestion.


Note

Docs update (webhooks troubleshooting)

  • Formats Message Status as bolded bullet points for clarity
  • Revises Multiple messages recovery guidance to state messages are sent at once with delays between them; adds link to endpoint rate limits and removes support-escalation note

Written by Cursor Bugbot for commit 3c34c1e. This will update automatically on new commits. Configure here.

Formatting suggestions
@vercel
Copy link

vercel bot commented Jul 15, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
codat-docs Ready Ready Preview, Comment Dec 23, 2025 5:23pm

@pj-simpson pj-simpson enabled auto-merge July 15, 2025 09:39
@github-actions
Copy link

github-actions bot commented Jul 15, 2025

Overall readability score: 58.04 (🟢 +0)

File Readability
troubleshooting.md 67.56 (🟢 +0)
View detailed metrics

🟢 - Shows an increase in readability
🔴 - Shows a decrease in readability

File Readability FRE GF ARI CLI DCRS
troubleshooting.md 67.56 64.71 10 8.7 8.81 8.59
  🟢 +0 🟢 +0 🟢 +0 🟢 +0 🟢 +0 🟢 +0

Averages:

  Readability FRE GF ARI CLI DCRS
Average 58.04 48.71 10.34 11.55 12.09 7.82
  🟢 +0 🟢 +0 🟢 +0 🟢 +0 🟢 +0 🟢 +0
View metric targets
Metric Range Ideal score
Flesch Reading Ease 100 (very easy read) to 0 (extremely difficult read) 60
Gunning Fog 6 (very easy read) to 17 (extremely difficult read) 8 or less
Auto. Read. Index 6 (very easy read) to 14 (extremely difficult read) 8 or less
Coleman Liau Index 6 (very easy read) to 17 (extremely difficult read) 8 or less
Dale-Chall Readability 4.9 (very easy read) to 9.9 (extremely difficult read) 6.9 or less

@pj-simpson pj-simpson merged commit a60fada into main Dec 23, 2025
6 of 11 checks passed
@pj-simpson pj-simpson deleted the pj-simpson-bold-list branch December 23, 2025 17:20
- "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.

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.

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).

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'.

@github-actions
Copy link

Link check results for preview deployment (https://codat-docs-git-pj-simpson-bold-list-codat.vercel.app):

[
  "[404] https://codat-docs-git-pj-simpson-bold-list-codat.vercel.app/"
]

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants