> For the complete documentation index, see [llms.txt](https://docs.tryterra.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tryterra.co/faq/help-topics/webhook/failures-errors-and-retries/retry-policy-and-redelivery.md).

# When are failed webhooks redelivered, and can I resend them?

**Failed webhook deliveries are retried automatically with exponential backoff** (roughly 5 min, 30 min, 1h, 2h, 4h, up to about 8 retries), always to your currently configured URL. All failures from an outage are generally resent within a little over 24 hours.

A failed user connection attempt is **not** retried. The user must re-run the connection flow.

Delivery status is visible in the dashboard debug log: failed attempts show their response codes and whether retries succeeded. You can also:

* manually resend any individual event from its details panel, or
* backfill missing data via the [REST API](https://docs.tryterra.co/health-and-fitness-api/managing-user-health-data/requesting-historical-data).

See [receiving data updates](https://docs.tryterra.co/health-and-fitness-api/managing-user-health-data/receiving-data-updates).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.tryterra.co/faq/help-topics/webhook/failures-errors-and-retries/retry-policy-and-redelivery.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.