Who needs it: Developers and IT teams building integrations (this visitor: Whirlpool Corporation)
What is missing
Webhooks are not mentioned anywhere on the page.
How many times a failed webhook delivery is retried, and on what schedule, is not stated.
What happens to deliveries that still fail after the last retry is not stated.
Whether failed deliveries can be seen or replayed is not stated.
Where
New section on /platform, placed after "The tools in Data Hub".
Related sections
Data syncs · Your data, connected and under control · Change history
Main topics
API coverage · webhook events available · retry attempts and backoff schedule · handling of permanently failed deliveries · viewing and replaying failed deliveries · link to developer documentation
What to do
Confirm with engineering the webhook retry count, backoff schedule, final-failure behaviour and any replay option.
Write and publish the section with these facts and a link to the developer documentation.
Done when: /platform has a section that states how webhook deliveries are retried and what happens when they keep failing.
Who needs it: Developers and IT teams building integrations
What is missing
Data Hub's product page does not mention webhooks or event delivery.
There is no link to where webhook reliability and retries are explained.
Where
Update this section: add a line under "Two-way syncs, without custom code" beside "Read-only fields where you need them".
Related sections
The tools in Data Hub
What to do
Add a line naming webhooks as a way to receive record changes.
Link that line to the new API and webhooks section on /platform.
Done when: /products/data mentions webhooks and links to the section explaining their retries. Depends on: “Add an API and webhooks section to /platform”
Answer full page
Webhook retries are covered in the Hourglass docs, which explain what happens when your endpoint is down and what becomes of failed deliveries. You'll find the details in the article linked below.